Locating equipment docking station communicatively coupled to or equipped with a mobile/portable device

ABSTRACT

A docking station to dock locating equipment (e.g., marking devices, locate devices, combined locate and marking devices) may be communicatively coupled to and/or equipped with a mobile/portable device (e.g., a mobile phone, personal digital assistant or other portable computing device) that provides processing, electronic storage, electronic display, user interface, communication facilities and/or other functionality (e.g., GPS-enabled functionality) for the docking station. A mobile/portable device may be mechanically and/or electrically coupled to the docking station. The mobile/portable device may provide redundant, shared and/or backup functionality for the docking station to enhance robustness. In one example, the mobile/portable device itself serves as a docking station for the locating equipment.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims a priority benefit, under 35 U.S.C. §120,as a continuation (CON) of U.S. non provisional application Ser. No.13/017,880, filed Jan. 31, 2011, entitled “Locating Equipment DockingStation Communicatively Coupled to or Equipped with a Mobile/PortableDevice.”

Ser. No. 13/017,880 in turn claims a priority benefit, under 35 U.S.C.§119(e), to U.S. provisional application Ser. No. 61/299,492, filed Jan.29, 2010, entitled “Marking Device Docking Stations and Methods of UsingSame.”

Each of the above-identified applications is hereby incorporated hereinby reference in its entirety.

BACKGROUND

Some types of field technicians, such as land surveyors and undergroundutility location technicians, use various types of marking materials toidentify specific locations on the ground during their field work. Forthis purpose, the field technician may employ a “marking device” todispense a marking material on the ground, pavement, or other surface.Marking material may be any material, substance, compound, and/orelement, used separately or in combination to mark, signify, and/orindicate. Examples of marking materials may include, but are not limitedto, paint, chalk, dye, and/or iron. Marking devices, such as paintmarking wands and/or paint marking wheels, provide a convenient methodof dispensing marking materials onto surfaces such as ground orpavement.

Conventional marking devices such as paint marking wands and/or paintmarking wheels are relatively simple mechanical devices withoutelectronic components, and hence are relatively inexpensive.Accordingly, the cost of individual marking devices generally isconsidered insignificant by the field technician using the device.Consequently, users/technicians may not take due care when handling suchmarking devices. As a result, marking devices are often mishandled,broken, or left behind in the field.

Further, users/technicians may carelessly stow marking devices in theirvehicles. For example, users/technicians often toss marking devices intovehicles and leave them unsecured. In the event of a vehicle accident,the marking device may be thrown about the vehicle cab and cause injuryto the passengers.

SUMMARY

The Applicants have designed significantly improved marking devices tofacilitate more reliable and efficient performance of markingoperations. Such marking devices also enable acquisition of variousfield information relating to use of the marking device and performanceof marking operations, and storage and transmission of such informationfor analytical (e.g., quality assessment) and/or archival purposes.Examples of such marking devices are described in the followingpublished U.S. applications: U.S. publication no. 2008-0228294-A1,published Sep. 18, 2008, filed Mar. 13, 2007, and entitled “MarkingSystem and Method With Location and/or Time Tracking;” U.S. publicationno. 2008-0245299-A1, published Oct. 9, 2008, filed Apr. 4, 2007, andentitled “Marking System and Method;” U.S. publication no. 2010-0086677A1, published Apr. 8, 2010, filed Aug. 11, 2009, and entitled, “Methodsand Apparatus for Generating an Electronic Record of a Marking OperationIncluding Service-Related Information and Ticket Information;” U.S.publication no. 2010-0088032-A1, published Apr. 8, 2010, filed Sep. 29,2009, and entitled, “Methods, Apparatus and Systems for GeneratingElectronic Records of Locate And Marking Operations, and Combined Locateand Marking Apparatus for Same;” and U.S. publication no. 2010-0189887A1, published Jul. 29, 2010, filed Feb. 11, 2010, and entitled “MarkingApparatus Having Enhanced Features for Underground Facility MarkingOperations, and Associated Methods and Systems,” each of whichpublications is incorporated herein by reference.

As marking devices become more complex and incorporate additionalfunctions, these devices become more costly. Accordingly, Applicantshave recognized and appreciated that approaches are needed to providebetter ways of handling and keeping track of marking devices in thefield. Similarly, as increased functionality is incorporated intomarking devices, it is desirable to provide methods of managing data andpower requirements of the marking devices in the field.

In view of the foregoing, various inventive embodiments disclosed hereinrelate to docking stations for use with such marking devices and tomethods for using the docking station with a marking device. In variousaspects, the docking station may serve as a home base for storage of amarking device, for charging the battery of a marking device, forfacilitating data transfer to and from a marking device, and/or forsecuring a marking device against unauthorized use and/or theft. In someembodiments, the docking station may be a mobile docking station that isinstalled in a vehicle. In other embodiments, the docking station may bea fixed docking station that is installed in a central location in thefield, at a central office, at a home base facility, and the like.

In some embodiments, a docking station may be communicatively coupled toand/or equipped with a mobile/portable device (e.g., a mobile computingdevice), such as a cellular phone or personal digital assistant (PDA),that provides processing, electronic storage, electronic display, userinterface, communication facilities, and/or other functionality (e.g.,GPS-enabled functionality) for the docking station. In some exemplaryimplementations, the mobile/portable device may provide essentially allof the processing and related functionality required to operate thedocking station, while in other implementations the mobile/portabledevice may only provide some portion of the overall functionality. Inyet other implementations, the mobile/portable device may provideredundant, shared and/or backup functionality for the docking station toenhance robustness.

In one exemplary implementation, a mobile/portable device may bemechanically coupled to the docking station (e.g., via an appropriatemobile device cradle, harness, or other attachment arrangement) orotherwise integrated with the docking station and communicativelycoupled to the docking station (e.g., via one or more wired or wirelessconnections), so as to permit one or more electronic signals to becommunicated between the mobile/portable device and other components ofthe docking station.

In some exemplary implementations, one or more electronic signalsindicative of operation of the docking station may be supplied by one ormore components of the docking station to the mobile/portable device. Inother aspects, the mobile/portable device may be appropriatelyprogrammed so as to log and generate electronic records of variouslocate information, marking information, and or landmark information,obtained from one or more pieces of locating equipment (e.g., markingdevices, combined marking and locating devices) communicatively coupledto the docking station. Such records may be formatted in variousmanners, processed and/or analyzed on the mobile/portable device, and/ortransmitted to another device (e.g., a remote computer/server) forstorage, processing and/or analysis. In one example, one or more piecesof geo-location data (e.g., from a GPS receiver, which may be integratedinto the mobile/portable device) are collected and logged on themobile/portable device. A computer-generated image or other visualrepresentation of a locate and/or marking operation may beelectronically rendered in a display field of the mobile/portable devicebased on logged locate information, marking information, and/or landmarkinformation.

In sum, one embodiment of the present invention is directed to anapparatus comprising a docking station to dock locating equipment of thetype used to locate and/or mark a presence or an absence of anunderground facility. The docking station comprises a mobile deviceinterface to facilitate mechanical, electrical and/or communicativecoupling of a mobile or portable computing device to the dockingstation.

Another embodiment is directed to a system comprising theabove-mentioned docking station and the mobile or portable computingdevice communicatively coupled to the docking station via the mobiledevice interface.

Another embodiment is directed to a method for docking locatingequipment of the type used to locate and/or mark a presence or anabsence of an underground facility. The method comprises: mechanically,electronically and/or communicatively coupling the locating equipment toa docking station; and performing one or more operations of the dockingstation using a mobile or computing device communicatively coupled tothe docking station.

Another embodiment is directed to a docking station for docking amarking device of the type used to mark a presence or an absence of anunderground facility. The docking station comprises a mobile computingdevice including an electronic interface configured to transferinformation to and from the marking device, the mobile computing deviceprogrammed to perform at least one operation involving communicationwith the marking device and functioning as a docking station for themarking device.

Another embodiment is directed to a method for operating a markingdevice of the type used to mark a presence or an absence of anunderground facility. The method comprises: electronically coupling amobile computing device to the marking device; and transferringinformation to and between the marking device and the mobile computingdevice, wherein the mobile computing device functions as a dockingstation for the marking device.

Another embodiment is directed to a system, comprising a marking deviceconfigured to mark a presence or an absence of an underground facility,and a mobile computing device communicatively coupled to the markingdevice, wherein the mobile computing device functions as a dockingstation for the marking device.

For purposes of the present disclosure, the term “dig area” refers to aspecified area of a work site within which there is a plan to disturbthe ground (e.g., excavate, dig holes and/or trenches, bore, etc.), andbeyond which there is no plan to excavate in the immediate surroundings.Thus, the metes and bounds of a dig area are intended to providespecificity as to where some disturbance to the ground is planned at agiven work site. It should be appreciated that a given work site mayinclude multiple dig areas.

The term “facility” refers to one or more lines, cables, fibers,conduits, transmitters, receivers, or other physical objects orstructures capable of or used for carrying, transmitting, receiving,storing, and providing utilities, energy, data, substances, and/orservices, and/or any combination thereof. The term “undergroundfacility” means any facility beneath the surface of the ground. Examplesof facilities include, but are not limited to, oil, gas, water, sewer,power, telephone, data transmission, cable television (TV), and/orinternet services.

The term “locate device” refers to any apparatus and/or device fordetecting and/or inferring the presence or absence of any facility,including without limitation, any underground facility. In variousexamples, a locate device may include both a locate transmitter and alocate receiver (which in some instances may also be referred tocollectively as a “locate instrument set,” or simply “locate set”).

The term “marking device” refers to any apparatus, mechanism, or otherdevice that employs a marking dispenser for causing a marking materialand/or marking object to be dispensed, or any apparatus, mechanism, orother device for electronically indicating (e.g., logging in memory) alocation, such as a location of an underground facility. Additionally,the term “marking dispenser” refers to any apparatus, mechanism, orother device for dispensing and/or otherwise using, separately or incombination, a marking material and/or a marking object. An example of amarking dispenser may include, but is not limited to, a pressurized canof marking paint. The term “marking material” means any material,substance, compound, and/or element, used or which may be usedseparately or in combination to mark, signify, and/or indicate. Examplesof marking materials may include, but are not limited to, paint, chalk,dye, and/or iron. The term “marking object” means any object and/orobjects used or which may be used separately or in combination to mark,signify, and/or indicate. Examples of marking objects may include, butare not limited to, a flag, a dart, and arrow, and/or an RFID markingball. It is contemplated that marking material may include markingobjects. It is further contemplated that the terms “marking materials”or “marking objects” may be used interchangeably in accordance with thepresent disclosure.

The term “locate mark” means any mark, sign, and/or object employed toindicate the presence or absence of any underground facility. Examplesof locate marks may include, but are not limited to, marks made withmarking materials, marking objects, global positioning or otherinformation, and/or any other means. Locate marks may be represented inany form including, without limitation, physical, visible, electronic,and/or any combination thereof.

The terms “actuate” or “trigger” (verb form) are used interchangeably torefer to starting or causing any device, program, system, and/or anycombination thereof to work, operate, and/or function in response tosome type of signal or stimulus. Examples of actuation signals orstimuli may include, but are not limited to, any local or remote,physical, audible, inaudible, visual, non-visual, electronic,mechanical, electromechanical, biomechanical, biosensing or othersignal, instruction, or event. The terms “actuator” or “trigger” (nounform) are used interchangeably to refer to any method or device used togenerate one or more signals or stimuli to cause or causing actuation.Examples of an actuator/trigger may include, but are not limited to, anyform or combination of a lever, switch, program, processor, screen,microphone for capturing audible commands, and/or other device ormethod. An actuator/trigger may also include, but is not limited to, adevice, software, or program that responds to any movement and/orcondition of a user, such as, but not limited to, eye movement, brainactivity, heart rate, other data, and/or the like, and generates one ormore signals or stimuli in response thereto. In the case of a markingdevice or other marking mechanism (e.g., to physically or electronicallymark a facility or other feature), actuation may cause marking materialto be dispensed, as well as various data relating to the markingoperation (e.g., geographic location, time stamps, characteristics ofmaterial dispensed, etc.) to be logged in an electronic file stored inmemory. In the case of a locate device or other locate mechanism (e.g.,to physically locate a facility or other feature), actuation may cause adetected signal strength, signal frequency, depth, or other informationrelating to the locate operation to be logged in an electronic filestored in memory.

The terms “locate and marking operation,” “locate operation,” and“locate” generally are used interchangeably and refer to any activity todetect, infer, and/or mark the presence or absence of an undergroundfacility. In some contexts, the term “locate operation” is used to morespecifically refer to detection of one or more underground facilities,and the term “marking operation” is used to more specifically refer tousing a marking material and/or one or more marking objects to mark apresence or an absence of one or more underground facilities. The term“locate technician” refers to an individual performing a locateoperation. A locate and marking operation often is specified inconnection with a dig area, at least a portion of which may be excavatedor otherwise disturbed during excavation activities.

The term “user” refers to an individual utilizing a locate device and/ora marking device and may include, but is not limited to, land surveyors,locate technicians, and support personnel.

The term “power source” refers to an apparatus, a device, a system,and/or any other means, and/or any combination thereof that generates,transmits, converts, and/or supplies power or energy, including, but notlimited to, electrical power.

The following U.S. published applications are hereby incorporated hereinby reference:

U.S. Pat. No. 7,640,105, issued Dec. 29, 2009, filed Mar. 13, 2007, andentitled “Marking System and Method With Location and/or Time Tracking;”

U.S. publication no. 2010-0094553-A1, published Apr. 15, 2010, filedDec. 16, 2009, and entitled “Systems and Methods for Using Location Dataand/or Time Data to Electronically Display Dispensing of Markers by AMarking System or Marking Tool;”

U.S. publication no. 2008-0245299-A1, published Oct. 9, 2008, filed Apr.4, 2007, and entitled “Marking System and Method;”

U.S. publication no. 2009-0013928-A1, published Jan. 15, 2009, filedSep. 24, 2008, and entitled “Marking System and Method;”

U.S. publication no. 2010-0090858-A1, published Apr. 15, 2010, filedDec. 16, 2009, and entitled “Systems and Methods for Using MarkingInformation to Electronically Display Dispensing of Markers by a MarkingSystem or Marking Tool;”

U.S. publication no. 2009-0238414-A1, published Sep. 24, 2009, filedMar. 18, 2008, and entitled “Virtual White Lines for Delimiting PlannedExcavation Sites;”

U.S. publication no. 2009-0241045-A1, published Sep. 24, 2009, filedSep. 26, 2008, and entitled “Virtual White Lines for Delimiting PlannedExcavation Sites;”

U.S. publication no. 2009-0238415-A1, published Sep. 24, 2009, filedSep. 26, 2008, and entitled “Virtual White Lines for Delimiting PlannedExcavation Sites;”

U.S. publication no. 2009-0241046-A1, published Sep. 24, 2009, filedJan. 16, 2009, and entitled “Virtual White Lines for Delimiting PlannedExcavation Sites;”

U.S. publication no. 2009-0238416-A1, published Sep. 24, 2009, filedJan. 16, 2009, and entitled “Virtual White Lines for Delimiting PlannedExcavation Sites;”

U.S. publication no. 2009-0237408-A1, published Sep. 24, 2009, filedJan. 16, 2009, and entitled “Virtual White Lines for Delimiting PlannedExcavation Sites;”

U.S. publication no. 2009-0202101-A1, published Aug. 13, 2009, filedFeb. 12, 2008, and entitled “Electronic Manifest of Underground FacilityLocate Marks;”

U.S. publication no. 2009-0202110-A1, published Aug. 13, 2009, filedSep. 11, 2008, and entitled “Electronic Manifest of Underground FacilityLocate Marks;”

U.S. publication no. 2009-0201311-A1, published Aug. 13, 2009, filedJan. 30, 2009, and entitled “Electronic Manifest of Underground FacilityLocate Marks;”

U.S. publication no. 2009-0202111-A1, published Aug. 13, 2009, filedJan. 30, 2009, and entitled “Electronic Manifest of Underground FacilityLocate Marks;”

U.S. publication no. 2009-0204625-A1, published Aug. 13, 2009, filedFeb. 5, 2009, and entitled “Electronic Manifest of Underground FacilityLocate Operation;”

U.S. publication no. 2009-0204466-A1, published Aug. 13, 2009, filedSep. 4, 2008, and entitled “Ticket Approval System For and Method ofPerforming Quality Control In Field Service Applications;”

U.S. publication no. 2009-0207019-A1, published Aug. 20, 2009, filedApr. 30, 2009, and entitled “Ticket Approval System For and Method ofPerforming Quality Control In Field Service Applications;”

U.S. publication no. 2009-0210284-A1, published Aug. 20, 2009, filedApr. 30, 2009, and entitled “Ticket Approval System For and Method ofPerforming Quality Control In Field Service Applications;”

U.S. publication no. 2009-0210297-A1, published Aug. 20, 2009, filedApr. 30, 2009, and entitled “Ticket Approval System For and Method ofPerforming Quality Control In Field Service Applications;”

U.S. publication no. 2009-0210298-A1, published Aug. 20, 2009, filedApr. 30, 2009, and entitled “Ticket Approval System For and Method ofPerforming Quality Control In Field Service Applications;”

U.S. publication no. 2009-0210285-A1, published Aug. 20, 2009, filedApr. 30, 2009, and entitled “Ticket Approval System For and Method ofPerforming Quality Control In Field Service Applications;”

U.S. publication no. 2009-0324815-A1, published Dec. 31, 2009, filedApr. 24, 2009, and entitled “Marking Apparatus and Marking Methods UsingMarking Dispenser with Machine-Readable ID Mechanism;”

U.S. publication no. 2010-0006667-A1, published Jan. 14, 2010, filedApr. 24, 2009, and entitled, “Marker Detection Mechanisms for use inMarking Devices And Methods of Using Same;”

U.S. publication no. 2010-0085694 A1, published Apr. 8, 2010, filed Sep.30, 2009, and entitled, “Marking Device Docking Stations and Methods ofUsing Same;”

U.S. publication no. 2010-0085701 A1, published Apr. 8, 2010, filed Sep.30, 2009, and entitled, “Marking Device Docking Stations Having SecurityFeatures and Methods of Using Same;”

U.S. publication no. 2010-0084532 A1, published Apr. 8, 2010, filed Sep.30, 2009, and entitled, “Marking Device Docking Stations HavingMechanical Docking and Methods of Using Same;”

U.S. publication no. 2010-0088032-A1, published Apr. 8, 2010, filed Sep.29, 2009, and entitled, “Methods, Apparatus and Systems for GeneratingElectronic Records of Locate And Marking Operations, and Combined Locateand Marking Apparatus for Same;”

U.S. publication no. 2010-0117654 A1, published May 13, 2010, filed Dec.30, 2009, and entitled, “Methods and Apparatus for Displaying anElectronic Rendering of a Locate and/or Marking Operation Using DisplayLayers;”

U.S. publication no. 2010-0086677 A1, published Apr. 8, 2010, filed Aug.11, 2009, and entitled, “Methods and Apparatus for Generating anElectronic Record of a Marking Operation Including Service-RelatedInformation and Ticket Information;”

U.S. publication no. 2010-0086671 A1, published Apr. 8, 2010, filed Nov.20, 2009, and entitled, “Methods and Apparatus for Generating anElectronic Record of A Marking Operation Including Service-RelatedInformation and Ticket Information;”

U.S. publication no. 2010-0085376 A1, published Apr. 8, 2010, filed Oct.28, 2009, and entitled, “Methods and Apparatus for Displaying anElectronic Rendering of a Marking Operation Based on an ElectronicRecord of Marking Information;”

U.S. publication no. 2010-0088164-A1, published Apr. 8, 2010, filed Sep.30, 2009, and entitled, “Methods and Apparatus for Analyzing Locate andMarking Operations with Respect to Facilities Maps;”

U.S. publication no. 2010-0088134 A1, published Apr. 8, 2010, filed Oct.1, 2009, and entitled, “Methods and Apparatus for Analyzing Locate andMarking Operations with Respect to Historical Information;”

U.S. publication no. 2010-0088031 A1, published Apr. 8, 2010, filed Sep.28, 2009, and entitled, “Methods and Apparatus for Generating anElectronic Record of Environmental Landmarks Based on Marking DeviceActuations;”

U.S. publication no. 2010-0188407 A1, published Jul. 29, 2010, filedFeb. 5, 2010, and entitled “Methods and Apparatus for Displaying andProcessing Facilities Map Information and/or Other Image Information ona Marking Device;”

U.S. publication no. 2010-0198663 A1, published Aug. 5, 2010, filed Feb.5, 2010, and entitled “Methods and Apparatus for Overlaying ElectronicMarking Information on Facilities Map Information and/or Other ImageInformation Displayed on a Marking Device;”

U.S. publication no. 2010-0188215 A1, published Jul. 29, 2010, filedFeb. 5, 2010, and entitled “Methods and Apparatus for Generating Alertson a Marking Device, Based on Comparing Electronic Marking Informationto Facilities Map Information and/or Other Image Information;”

U.S. publication no. 2010-0188088 A1, published Jul. 29, 2010, filedFeb. 5, 2010, and entitled “Methods and Apparatus for Displaying andProcessing Facilities Map Information and/or Other Image Information ona Locate Device;”

U.S. publication no. 2010-0189312 A1, published Jul. 29, 2010, filedFeb. 5, 2010, and entitled “Methods and Apparatus for OverlayingElectronic Locate Information on Facilities Map Information and/or OtherImage Information Displayed on a Locate Device;”

U.S. publication no. 2010-0188216 A1, published Jul. 29, 2010, filedFeb. 5, 2010, and entitled “Methods and Apparatus for Generating Alertson a Locate Device, Based ON Comparing Electronic Locate Information TOFacilities Map Information and/or Other Image Information;”

U.S. publication no. 2010-0189887 A1, published Jul. 29, 2010, filedFeb. 11, 2010, and entitled “Marking Apparatus Having Enhanced Featuresfor Underground Facility Marking Operations, and Associated Methods andSystems;”

U.S. publication no. 2010-0188245 A1, published Jul. 29, 2010, filedFeb. 11, 2010, and entitled “Locate Apparatus Having Enhanced Featuresfor Underground Facility Locate Operations, and Associated Methods andSystems;”

U.S. publication no. 2009-0204238-A1, published Aug. 13, 2009, filedFeb. 2, 2009, and entitled “Electronically Controlled Marking Apparatusand Methods;”

U.S. publication no. 2009-0208642-A1, published Aug. 20, 2009, filedFeb. 2, 2009, and entitled “Marking Apparatus and Methods For Creatingan Electronic Record of Marking Operations;”

U.S. publication no. 2009-0210098-A1, published Aug. 20, 2009, filedFeb. 2, 2009, and entitled “Marking Apparatus and Methods For Creatingan Electronic Record of Marking Apparatus Operations;”

U.S. publication no. 2009-0201178-A1, published Aug. 13, 2009, filedFeb. 2, 2009, and entitled “Methods For Evaluating Operation of MarkingApparatus;”

U.S. publication no. 2009-0238417-A1, published Sep. 24, 2009, filedFeb. 6, 2009, and entitled “Virtual White Lines for Indicating PlannedExcavation Sites on Electronic Images;”

U.S. publication no. 2010-0205264-A1, published Aug. 12, 2010, filedFeb. 10, 2010, and entitled “Methods, Apparatus, and Systems forExchanging Information Between Excavators and Other Entities Associatedwith Underground Facility Locate and Marking Operations;”

U.S. publication no. 2010-0205031-A1, published Aug. 12, 2010, filedFeb. 10, 2010, and entitled “Methods, Apparatus, and Systems forExchanging Information Between Excavators and Other Entities Associatedwith Underground Facility Locate and Marking Operations;”

U.S. publication no. 2010-0201706-A1, published Aug. 12, 2010, filedJun. 1, 2009, and entitled “Virtual White Lines (VWL) for DelimitingPlanned Excavation Sites of Staged Excavation Projects;”

U.S. publication no. 2010-0205555-A1, published Aug. 12, 2010, filedJun. 1, 2009, and entitled “Virtual White Lines (VWL) for DelimitingPlanned Excavation Sites of Staged Excavation Projects;”

U.S. publication no. 2010-0205195-A1, published Aug. 12, 2010, filedJun. 1, 2009, and entitled “Methods and Apparatus for Associating aVirtual White Line (VWL) Image with Corresponding Ticket Information foran Excavation Project;”

U.S. publication no. 2010-0205536-A1, published Aug. 12, 2010, filedJun. 1, 2009, and entitled “Methods and Apparatus for Controlling Accessto a Virtual White Line (VWL) Image for an Excavation Project;”

U.S. publication no. 2010-0228588-A1, published Sep. 9, 2010, filed Feb.11, 2010, and entitled “Management System, and Associated Methods andApparatus, for Providing Improved Visibility, Quality Control and AuditCapability for Underground Facility Locate and/or Marking Operations;”

U.S. publication no. 2010-0201690-A1, published Aug. 12, 2010, filedApr. 13, 2009, and entitled “Virtual White Lines (VWL) Application forIndicating a Planned Excavation or Locate Path;”

U.S. publication no. 2010-0205554-A1, published Aug. 12, 2010, filedApr. 13, 2009, and entitled “Virtual White Lines (VWL) Application forIndicating an Area of Planned Excavation;”

U.S. publication no. 2009-0202112-A1, published Aug. 13, 2009, filedFeb. 11, 2009, and entitled “Searchable Electronic Records ofUnderground Facility Locate Marking Operations;”

U.S. publication no. 2009-0204614-A1, published Aug. 13, 2009, filedFeb. 11, 2009, and entitled “Searchable Electronic Records ofUnderground Facility Locate Marking Operations;”

U.S. publication no. 2010-0205032-A1, published Aug. 12, 2010, filedFeb. 11, 2010, and entitled “Marking Apparatus Equipped with TicketProcessing Software for Facilitating Marking Operations, and AssociatedMethods;”

U.S. publication no. 2009-0327024-A1, published Dec. 31, 2009, filedJun. 26, 2009, and entitled “Methods and Apparatus for QualityAssessment of a Field Service Operation;”

U.S. publication no. 2010-0010862-A1, published Jan. 14, 2010, filedAug. 7, 2009, and entitled, “Methods and Apparatus for QualityAssessment of a Field Service Operation Based on GeographicInformation;”

U.S. publication No. 2010-0010863-A1, published Jan. 14, 2010, filedAug. 7, 2009, and entitled, “Methods and Apparatus for QualityAssessment of a Field Service Operation Based on Multiple ScoringCategories;”

U.S. publication no. 2010-0010882-A1, published Jan. 14, 2010, filedAug. 7, 2009, and entitled, “Methods and Apparatus for QualityAssessment of a Field Service Operation Based on Dynamic AssessmentParameters;”

U.S. publication no. 2010-0010883-A1, published Jan. 14, 2010, filedAug. 7, 2009, and entitled, “Methods and Apparatus for QualityAssessment of a Field Service Operation Based on Multiple QualityAssessment Criteria;”

U.S. publication no. 2010-0088135 A1, published Apr. 8, 2010, filed Oct.1, 2009, and entitled, “Methods and Apparatus for Analyzing Locate andMarking Operations with Respect to Environmental Landmarks;”

U.S. publication no. 2010-0085185 A1, published Apr. 8, 2010, filed Sep.30, 2009, and entitled, “Methods and Apparatus for Generating ElectronicRecords of Locate Operations;”

U.S. publication no. 2010-0090700-A1, published Apr. 15, 2010, filedOct. 30, 2009, and entitled “Methods and Apparatus for Displaying anElectronic Rendering of a Locate Operation Based on an Electronic Recordof Locate Information;”

U.S. publication no. 2010-0085054 A1, published Apr. 8, 2010, filed Sep.30, 2009, and entitled, “Systems and Methods for Generating ElectronicRecords of Locate And Marking Operations;”

U.S. publication no. 2010-0256825-A1, published Oct. 7, 2010, filed Jun.9, 2010, and entitled “Marking Apparatus Having Operational Sensors ForUnderground Facility Marking Operations, And Associated Methods AndSystems;”

U.S. publication no. 2010-0255182-A1, published Oct. 7, 2010, filed Jun.9, 2010, and entitled “Marking Apparatus Having Operational Sensors ForUnderground Facility Marking Operations, And Associated Methods AndSystems;”

U.S. publication no. 2010-0245086-A1, published Sep. 30, 2010, filedJun. 9, 2010, and entitled “Marking Apparatus Configured To DetectOut-Of-Tolerance Conditions In Connection With Underground FacilityMarking Operations, And Associated Methods And Systems;”

U.S. publication no. 2010-0247754-A1, published Sep. 30, 2010, filedJun. 9, 2010, and entitled “Methods and Apparatus For Dispensing MarkingMaterial In Connection With Underground Facility Marking OperationsBased on Environmental Information and/or Operational Information;”

U.S. publication no. 2010-0262470-A1, published Oct. 14, 2010, filedJun. 9, 2010, and entitled “Methods, Apparatus, and Systems ForAnalyzing Use of a Marking Device By a Technician To Perform AnUnderground Facility Marking Operation;”

U.S. publication no. 2010-0263591-A1, published Oct. 21, 2010, filedJun. 9, 2010, and entitled “Marking Apparatus Having EnvironmentalSensors and Operations Sensors for Underground Facility MarkingOperations, and Associated Methods and Systems;”

U.S. publication no. 2010-0253511-A1, published Oct. 7, 2010, filed Jun.18, 2010, and entitled “Locate Apparatus Configured to DetectOut-of-Tolerance Conditions in Connection with Underground FacilityLocate Operations, and Associated Methods and Systems;”

U.S. publication no. 2010-0257029-A1, published Oct. 7, 2010, filed Jun.18, 2010, and entitled “Methods, Apparatus, and Systems For AnalyzingUse of a Locate Device By a Technician to Perform an UndergroundFacility Locate Operation;”

U.S. publication no. 2010-0253513-A1, published Oct. 7, 2010, filed Jun.18, 2010, and entitled “Locate Transmitter Having Enhanced Features ForUnderground Facility Locate Operations, and Associated Methods andSystems;”

U.S. publication no. 2010-0253514-A1, published Oct. 7, 2010, filed Jun.18, 2010, and entitled “Locate Transmitter Configured to DetectOut-of-Tolerance Conditions In Connection With Underground FacilityLocate Operations, and Associated Methods and Systems;”

U.S. publication no. 2010-0256912-A1, published Oct. 7, 2010, filed Jun.18, 2010, and entitled “Locate Apparatus for Receiving EnvironmentalInformation Regarding Underground Facility Marking Operations, andAssociated Methods and Systems;”

U.S. publication no. 2010-0259381-A1, published Oct. 14, 2010, filedJun. 28, 2010, and entitled “Methods, Apparatus and Systems forNotifying Excavators and Other Entities of the Status of in-ProgressUnderground Facility Locate and Marking Operations;”

U.S. publication no. 2010-0262670-A1, published Oct. 14, 2010, filedJun. 28, 2010, and entitled “Methods, Apparatus and Systems forCommunicating Information Relating to the Performance of UndergroundFacility Locate and Marking Operations to Excavators and OtherEntities;”

U.S. publication no. 2010-0259414-A1, published Oct. 14, 2010, filedJun. 28, 2010, and entitled “Methods, Apparatus And Systems ForSubmitting Virtual White Line Drawings And Managing Notifications InConnection With Underground Facility Locate And Marking Operations;”

U.S. publication no. 2010-0268786-A1, published Oct. 21, 2010, filedJun. 28, 2010, and entitled “Methods, Apparatus and Systems forRequesting Underground Facility Locate and Marking Operations andManaging Associated Notifications;”

U.S. publication no. 2010-0257477-A1, published Oct. 7, 2010, filed Apr.2, 2010, and entitled “Methods, Apparatus, and Systems for Documentingand Reporting Events Via Time-Elapsed Geo-Referenced ElectronicDrawings;”

U.S. publication no. 2010-0256981-A1, published Oct. 7, 2010, filed Apr.2, 2010, and entitled “Methods, Apparatus, and Systems for Documentingand Reporting Events Via Time-Elapsed Geo-Referenced ElectronicDrawings;”

U.S. publication no. 2010-0285211-A1, published Nov. 11, 2010, filedApr. 21, 2010, and entitled “Method Of Using Coded Marking Patterns InUnderground Facilities Locate Operations.”

It should be appreciated that all combinations of the foregoing conceptsand additional concepts discussed in greater detail below (provided suchconcepts are not mutually inconsistent) are contemplated as being partof the inventive subject matter disclosed herein. In particular, allcombinations of claimed subject matter appearing at the end of thisdisclosure are contemplated as being part of the inventive subjectmatter disclosed herein. It should also be appreciated that terminologyexplicitly employed herein that also may appear in any disclosureincorporated by reference should be accorded a meaning most consistentwith the particular concepts disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The skilled artisan will understand that the figures, described herein,are for illustration purposes only, and that the drawings are notintended to limit the scope of the disclosed teachings in any way. Insome instances, various aspects or features may be shown exaggerated orenlarged to facilitate an understanding of the inventive conceptsdisclosed herein (the drawings are not necessarily to scale, emphasisinstead being placed upon illustrating the principles of the teachings).In the drawings, like reference characters generally refer to likefeatures, functionally similar and/or structurally similar elementsthroughout the various figures.

FIG. 1 is a schematic design of a docking station and a marking device,with the marking device removed from the docking station, according toembodiments of the invention;

FIG. 2 is a schematic diagram of a marking device attached to a dockingstation;

FIG. 3A is a simplified block diagram of a system that includes anelectronic docking station coupled to a marking device, in accordancewith embodiments of the invention;

FIG. 3B is a simplified block diagram of a system that includes anelectronic and mechanical docking station coupled to a marking device,in accordance with embodiments of the invention;

FIG. 3C is a simplified block diagram of a system that includes amechanical docking station coupled to a marking device, in accordancewith embodiments of the invention;

FIG. 4 is a schematic block diagram of docking station electronics, inaccordance with embodiments of the invention;

FIG. 5A is a top view of a portion of a docking station;

FIG. 5B is a side view of a portion of a docking station;

FIG. 6A is a side view of a portion of a marking device that may beattached to a docking station;

FIG. 6B is a bottom view of a portion of a marking device that may beattached to a docking station;

FIG. 7 is a side view of a marking device being attached to a dockingstation;

FIG. 8A is a top view of an exemplary vehicle configurationincorporating a docking station;

FIG. 8B is a top view of another exemplary vehicle configurationincorporating a docking station;

FIG. 8C is a schematic block diagram of a network system incorporating adocking station;

FIG. 9 is a flow diagram of a method of using a docking station;

FIG. 10 is a flow diagram of another method of using a docking station;

FIG. 11 is a schematic diagram of a marking device attached to a dockingstation, according to another embodiment of the invention;

FIG. 12 is a flow diagram of an additional method of using a dockingstation;

FIG. 13 is a schematic diagram of an exemplary configurationincorporating docking stations;

FIG. 14 is a perspective view of an embodiment of a docking station anda marking device, with the marking device removed from the dockingstation;

FIG. 15 is an enlarged perspective view of a portion of the dockingstation and marking device of FIG. 14;

FIG. 16 is a perspective view of the docking station with the markingdevice docked therein;

FIG. 17 is a perspective view of a marking device docking station thathas processing and communications capability, in accordance withembodiments of the invention;

FIG. 18 is a schematic diagram of multiple fixed marking device dockingstations in communication with a central computing device, which is oneexample of a docking station network, in accordance with embodiments ofthe invention;

FIG. 19 is a schematic diagram of multiple mobile marking device dockingstations in the field and in communication with an onsite computingdevice, which is another example of a docking station network, inaccordance with embodiments of the invention;

FIG. 20 is a schematic diagram of multiple mobile marking device dockingstations in the field and in communication with each other, which is yetanother example of a docking station network, in accordance withembodiments of the invention;

FIG. 21 is a schematic diagram of at least one marking device dockingstation in communication with at least one marking device, which isstill another example of a docking station network, in accordance withembodiments of the invention;

FIGS. 22A-22D are perspective views of exemplary mobile device-specificcradles integrated into a docking station, in accordance withembodiments of the invention;

FIGS. 23A and 23B are perspective views of an exemplary mobile deviceuniversal cradle integrated into a docking station, in accordance withembodiments of the invention;

FIGS. 24A and 24B are perspective views of an exemplary slot, pocket,and/or pouch in a docking station for holding a mobile device, inaccordance with embodiments of the invention;

FIG. 25 is a perspective view of exemplary mobile device-specificadaptors for use with a docking station, in accordance with embodimentsof the invention;

FIG. 26 is a perspective view of a user-worn mobile device incommunication with a docking station, in accordance with embodiments ofthe invention; and

FIG. 27 is a perspective view of a mobile device connected to a markingdevice, the mobile device functioning as a docking station for themarking device, in accordance with embodiments of the invention.

DETAILED DESCRIPTION

Following below are descriptions of various concepts related to, andinventive embodiments of, locating equipment docking stationscommunicatively coupled to and/or equipped with a mobile/portabledevice. It should be appreciated that various concepts introduced aboveand discussed in greater detail below may be implemented in any ofnumerous ways, as the disclosed concepts are not limited to anyparticular manner of implementation. Examples of specificimplementations and applications are provided primarily for illustrativepurposes.

In embodiments discussed below in connection with the figures, variousconcepts relating to docking stations for locating equipment areintroduced for purposes of illustration using a marking device as anexemplary piece of locating equipment. It should be appreciated,however, that the inventive concepts disclosed herein are not limited inthis respect, and that docking stations according to the presentdisclosure may be configured to facilitate docking (and variousfunctionality associated therewith) of various types of locatingequipment, examples of which include marking devices, locate devices,and combined locate and marking devices (as described in various U.S.publications incorporated herein by reference).

FIG. 1 illustrates a docking station 100 and a marking device 150,removed from docking station 100, according to one embodiment of thepresent invention. Docking station 100 may be installed in, for example,a vehicle and is suitable for use in conjunction with marking device150. In other embodiments, the docking station 100 may be installed at acentral facility, office or other fixed location. Thus, the dockingstation 100 may be mobile or fixed. Docking station 100 may serve as ahome base for storage of marking device 150 and for charging the batteryof marking device 150.

Docking station 100 may include a base 110 and a support housing 114.Base 110 and support housing 114 may be made of any suitably strong,rigid, and lightweight material. Such material may include, but is notlimited to, molded plastic and metal. Docking station 100 may bedesigned and constructed to be bolted to the body of a vehicle and maybe made of materials that prevent unauthorized removal from a vehicle.In the embodiment of FIG. 1, docking station 100 is configured andmounted to support marking device 150 in an upright, or vertical,position. In other embodiments, docking station may be configured andmounted to support marking device 150 in a horizontal position or in anyother position.

In an embodiment, a cradle 118 is integrated into the upper end ofsupport housing 114. This provides a mechanism to mechanically andelectrically couple marking device 150 to docking station 100. Otherembodiments illustrating a cradle that may be integrated into supporthousing 114 are described with reference to FIGS. 5A, 5B, 6A, 6B, and 7.

Electronic and electro-mechanical components that provide an interfacebetween a marking device, an external computing device, and/or a powersource may be installed in support housing 114. For example, dockingcontrol electronics 128, including a communications interface 122 and apower interface 126, may be installed in support housing 114.Communications interface 122 and power interface 126 may be the driveand buffer circuitry for supplying electrical signals and power,respectively, to cradle 118, which in turn supplies electrical signalsand power to marking device 150 when marking device 150 is attached todocking station 100. In the embodiment of FIG. 1, communicationsinterface 122 provides a wired connection to control electronics inmarking device 150. In other embodiments, docking station 100 mayinclude a wireless link to control electronics in marking device 150.Docking station 100 may supply electrical signals and power to anyconfiguration or embodiment of marking device 150, and marking device150 may receive electrical signals and power from any configuration orembodiment of docking station 100.

Docking control electronics 128 may include a processor and othercircuitry for managing and driving various user interface devices, suchas, but not limited to, indicators 130, manual controls 134, and audiooutput 138. Docking station 100 may include visible and/or audible meansof informing the user of status changes and other conditions requiringattention. Further, docking station 100 may include user controls thatallow a user to initiate activities, such as data synchronization (e.g.,uploading and downloading data). For example, indicators 130 may includeone or more light-emitting diode (LED) devices of specified colors andindicate a meaning to the user (e.g., red, green, and yellow batterystatus indicators; yellow and orange data synchronization statusindicators, and the like). Manual controls 134 may include one or moremanual push buttons for initiating various functions (e.g., an initiatedata synchronization push button). Audio output 138 may be, for example,an audio speaker, an audio alarm and/or buzzer. Docking controlelectronics 128 may include an audio input (not shown). For example, anaudio input, such as a microphone, may be incorporated into the dockingstation.

Docking control electronics 128 may also include a mechanism for shortrange identification, such as radio-frequency identification (RFID). Forexample, docking station 100 may include an RFID reader 129 for readingan RFID tag affixed to marking device 150. In another embodiment,docking station 100 may include a barcode reader for reading a barcodeaffixed to marking device 150.

The processor of docking control electronics 128 may be capable ofmanaging data transfer between marking device 150 and an externalcomputing device. For example, a wired connection 140, such as auniversal serial bus (USB) connection, RS232 connectors, RJ45connectors, Ethernet, and any combination thereof may be providedbetween docking control electronics 128 of docking station 100 and anexternal computing device. Further, the processor of docking controlelectronics 128 may be programmable to perform any user-definedfunction, such as, but not limited to, executing a security functionprogrammed to ensure that only authorized personnel may access and usemarking device 150 and/or docking station 100. Additionally, a wiredpower connection (not shown) may be provided for connecting dockingstation 100 to the power source of a vehicle in which it is installed.In this manner, the power source of a vehicle may in turn be used tocharge the battery of marking device 150 coupled to the docking station100.

Additionally, as shown in FIG. 1, a safety strap 142 for securingmarking device 150 in docking station 100 may be attached to supporthousing 114 of docking station 100. In one embodiment, a device,incorporated in safety strap 142, is capable of conducting an electricalsignal that may be detected by docking control electronics 128 toindicate whether safety strap 142 has been secured around marking device150. For example, a small tracer wire may be installed within safetystrap 142, which changes a logic state depending upon whether both endsor one end only is fastened to support housing 114. As described below,docking station 100 may include additional or different locking andsecurity devices.

Marking device 150 may be any marking device that has, for example,battery powered electronics incorporated therein for any functionality(e.g., global positioning system (GPS) technology, RFID technology, datastorage devices, electronic actuator, electronic display, markingmaterial sensing technology, wired and/or wireless communicationstechnology and the like). For example, marking device 150 may be amarking device as described in U.S. publication no. 2008-0228294-A1,published Sep. 18, 2008, filed Mar. 13, 2007, and entitled “MarkingSystem and Method With Location and/or Time Tracking;” U.S. publicationno. 2008-0245299-A1, published Oct. 9, 2008, filed Apr. 4, 2007, andentitled “Marking System and Method;” and U.S. publication no.2009-0204238-A1, published Aug. 13, 2009, filed Feb. 2, 2009, andentitled “Electronically Controlled Marking Apparatus and Methods;”which are incorporated by reference herein in their entirety.

It will be understood that the docking stations described herein can beused with other marking devices, including but not limited to markingdevices that have limited electronic capability and marking devices thathave no electronic capability. In some embodiments, the docking stationmay be used for holding, storage and/or locking of the marking device,without electronic functionality. In addition, the docking station maybe used for docking of a combination locate and marking device, whichincludes both locate and marking functions.

Marking device 150 may include a shaft 154, a handle 158, a markingdispenser holder 162, an actuator 166, control electronics 170, at leastone rechargeable battery 172 for powering control electronics 170, adocking station interface 174, and an RFID tag 178. Rechargeable battery172 may be a power source for the marking device 150. Rechargeablebatteries 172 may be, for example, rechargeable lithium ion batteries,which are sized according to the requirements of control electronics170. RFID tag 178 may store a unique identification code, which may beused to identify and track marking device 150.

A marking dispenser 180 (e.g., an aerosol marking paint canister) may beinstalled in marking dispenser holder 162 of marking device 150 asillustrated. Actuator 166 may be an electrical/mechanical actuator foractivating the marking material spray action of marking dispenser 180.

Control electronics 170 may include, but is not limited to, a processor,GPS technology, RFID technology, data storage devices, electronicactuator, electronic display, marking material sensing technology andwired and/or wireless communications technology (e.g., an Intranetconnection, Internet, Bluetooth® technology, Wi-Fi, Wi-Max, IEEE 802.11technology, radio frequency (RF), Infrared Data Association (IrDA)compatible protocols, Local Area Networks (LAN), Wide Area Networks(WAN), Shared Wireless Access Protocol (SWAP), combinations thereof, andother types of wireless networking protocols).

Docking station interface 174 of the marking device 150 is a mechanismthat is designed to fit the cradle 118 of docking station 100 so as toprovide a mechanical and electrical connection therebetween. Thephysical dimensions and shape of docking station interface 174 ofmarking device 150 substantially correspond to the physical dimensionsand shape of cradle 118 of docking station 100. Furthermore, electricalinputs/outputs (I/Os) (e.g., signal, data, and power), integrated intodocking station interface 174, are designed to connect to theircounterparts integrated in cradle 118 of docking station 100. An exampleof docking station interface 174 of marking device 150 is described withreference to FIGS. 5A, 5B, 6A, 6B, and 7.

FIG. 2 is a schematic diagram of marking device 150 attached to dockingstation 100, according to embodiments of the invention. Morespecifically, FIG. 2 depicts marking device 150 resting and retainedwithin a cavity of base 110 of docking station 100. Docking stationinterface 174 of marking device 150 is engaged with cradle 118 ofdocking station 100. Docking station 100 can be configured to dockmarking device 150 either with or without marking dispenser 180installed in marking device 150. Safety strap 142 may be fastened aroundshaft 154 of marking device 150 to hold marking device 150 securely, sothat the marking device remains mechanically and electrically coupled todocking station 100.

The docking station 100 shown in FIGS. 1 and 2 and described aboveprovides both mechanical and electronic docking of a marking device. Inparticular, the docking station 100 is mechanically coupled to themarking device 150 in the docked position and has docking stationelectronics 128 which communicate electronically with controlelectronics 170 in marking device 150. It will be understood, however,that the docking station may have a variety of configurations within thescope of the present invention. Accordingly, in additional figuresdiscussed below, generic examples of docking stations and/or markingdevices may be indicated using different reference numerals than thoseused for similar components/features illustrated in FIGS. 1 and 2.

Referring to FIG. 3A, a block diagram of an electronic docking station200 is shown. Docking station 200 includes docking control electronicscoupled by an electronic connection 206 to a marking device 202.Electronic connection 206 may be a wired connection, such as by a cableor electrical connector, or may be a wireless connection. Embodiments ofdocking control electronics for docking station 200 are described below.Docking station 200 may be connected to a computing device 204 via anelectronic connection 208, which may be a wired connection or a wirelessconnection. The computing device 204 may be an on-site computer, such asan in-vehicle computer, or may be a remote computer, such as a centraloffice computer. Docking station 200 provides electronic support ofmarking device 202 and supports such functions as data storage and/ortransfer, battery charging and diagnostics and calibration, for example.However, in the embodiment of FIG. 3A, docking station 200 is notmechanically coupled to marking device 202 and does not providemechanical support, storage or locking of marking device 202. Thephysical configuration of docking station 200 may be an electronicsenclosure or housing having suitable connectors, cables and/or antennasfor communication with marking device 202 and computing device 204, andoptional user interface components as described below.

Referring to FIG. 3B, a docking station 210 is mechanically andelectronically coupled to a marking device 212. An electronic connection216 between docking station 210 and marking device 212 may be a wiredconnection, such as by a cable or electrical connector, or may be awireless connection between docking station electronics and markingdevice electronics. Docking station 210 further includes a mechanicalconnection 217 to marking device 212. Mechanical connection 217 may havea variety of configurations, including, but not limited to, a holder tosupport and retain marking device 212, a locking mechanism that ismechanically or electronically controlled and/or a partial or completeenclosure for marking device 212. The partial or complete enclosure forthe marking device may provide security for the marking device and/ormay protect the marking device against exposure to weather conditions.The docking station 210 may provide mechanical support for markingdevice 212 in any desired position, such as vertical or horizontal, forexample, and may be fixed or mobile. Docking station 210 may include anelectronic connection 218 to a computing device 214, which may be localor remote as described above in connection with computing device 204.Electronic connection 218 may be a wired connection or a wirelessconnection. The docking station 100 shown in FIGS. 1 and 2 may be of thetype shown in FIG. 3B.

Referring to FIG. 3C, a docking station 220 is mechanically coupled to amarking device 222 by a mechanical connection 227. The mechanicalconnection between docking station 220 and marking device 222 may haveany desired mechanical configuration, including but not limited to aholder to support and retain marking device 222 in a desiredorientation, such as vertical or horizontal, a locking mechanism tosecure marking device 222 to docking station 220 and/or a partial orcomplete enclosure for marking device 222. The partial or completeenclosure for the marking device may provide security for the markingdevice and/or may protect the marking device against exposure to weatherconditions. In the embodiment of FIG. 3C, an electronic connection isnot provided between docking station 220 and marking device 222.Instead, marking device 222 may communicate directly with a computingdevice 224 via an electronic connection 228, which may be a wiredconnection or a wireless connection. Computing device 224 may be a localcomputer, such as an in-vehicle computer or may be a remote computer,such as a central office computer. The physical configuration of dockingstation 220 may be similar to docking station 100 shown in FIGS. 1 and2, with most or all electronic components omitted.

In each of FIGS. 3A, 3B and 3C, the electronic connection to thecomputing device is optional. The computing device may provide controlof the docking station and may receive marking device data, such as datafrom electronic records of marking operations. The marking device datamay be transferred by the docking station from the marking devicedirectly to the computing device and/or may be stored in a local memoryof the docking station. The data transfer may occur at the time ofdocking of the marking device or may occur at a later time, such as atthe end of the day. In other embodiments, the electronic connectionbetween the docking station and the computing device is omitted. Forexample, data can be transferred from the docking station to any desiredcomputing device by use of a removable memory.

In the embodiments of FIGS. 3A, 3B and 3C, the docking station mayprovide a battery charging function for the marking device. Thus, forexample, the docking station can be connected to a power source, such asan AC power source for fixed applications, or a DC source, such asvehicle power, for mobile applications. The docking station may includecircuitry for charging batteries in the marking device. In otherembodiments, a separate battery charger is connected directly to themarking device.

A block diagram of docking control electronics 250 in accordance withembodiments of the invention is shown in FIG. 4. Docking controlelectronics 250 may include components for managing the overalloperation of the docking stations described herein. Docking controlelectronics 250 may include a communication interface 252 forcommunication with a marking device, a communication interface 254 forcommunication with a local or remote computing device, and a userinterface 256 for interacting with a user by receiving user inputsand/or providing information to a user. Docking control electronics 250may further include a timing system 260 for timing of docking stationoperations and events, a location tracking system 262 for determininggeographical coordinates of the docking station and an ID reader 264 forreading an identification tag 265 on the marking device.

Docking control electronics 250 may further include a processor 266 andat least one memory 270. Memory 270 may be used for storage of controlsoftware and for data storage. It will be understood that memory 270 maybe configured as one or more memories, such as separate memories fordata storage and program storage. Memory 270 may include a data storagearea 290 for storage of data transferred from the marking device and/orother data involved in operation of the docking station.

Docking control electronics 250 may further include a battery controlcircuit 272 which receives AC or DC power from an external power source274 and performs charging of the battery of the marking device undercontrol of processor 266.

In some embodiments, docking control electronics 250 may include amemory connector (not shown) to permit connection of a memory device,such as a memory device containing data from the marking device. Infurther embodiments, docking control electronics 250 may include abattery connector (not shown) to permit connection of one or morebatteries from the marking device, for charging.

Control software, typically stored in memory 270, may include acommunication control module 280 to control communication with themarking device and with the computing device, and a data transfer module282 to perform data transfer to and between the marking device, a localmemory and the computing device. The control software may furtherinclude a battery control module 284 to control battery charging andrecording of battery information, a diagnostics module 286 to performdiagnostics and calibration of the marking device, as well asdiagnostics of the docking station itself. The control software mayfurther include a security module 288 that controls a locking mechanismand/or data transfer operations based on information including, but notlimited to, a table of approved marking device IDs, allowed andprohibited geographical coordinates and/or allowed and prohibited timesand dates.

Communication interface 252 may be any wired and/or wirelesscommunication interface by which information may be exchanged betweenthe docking station and a marking device. Similarly, communicationinterface 254 may be any wired and/or wireless communication interfaceby which information may be exchanged between the docking station and alocal or remote computing device. Examples of wired communicationinterfaces may include, but are not limited to, USB ports, RS232connectors, RJ45 connectors, Ethernet, and combinations thereof.Examples of wireless communication interfaces may include, but are notlimited to, Bluetooth® Technology, Wi-Fi, Wi-Max, IEEE 802.11Technology, Radio Frequency (RF), Local Area Networks (LAN) and WideArea Networks (WAN), Internet, Shared Wireless Access Protocol (SWAP),Infrared Data Association (IrDS) compatible protocols and other types ofwireless networking protocols, and combinations thereof.

User interface 256 may be any mechanism or combination of mechanisms bywhich the user may interact with the docking station. For example, userinterface 256 may include, but is not limited to, a display (includingintegrated displays and external displays, such as Heads-Up Displays(HUDs)), a touch screen, one or more manual pushbuttons, one or moretoggle switches, a keypad, and combinations thereof. In one example, thedisplay includes one or more liquid crystal displays (LCD) orlight-emitting diode (LED) displays that are suitably small for use in aportable device yet suitably large for ease of viewing. User interface256 may include standard zoom in and out controls for the display. Inone example, a display includes a 4.3 inch diagonal LCD. Preferably, thedisplay is at least 5 characters tall by 40 characters wide, is full-sundaylight readable and includes automatic backlighting for low lightapplications. In one implementation, the user interface 256 includes a“menu/on” button to power up the docking station and provide amenu-driven graphical user interface (GUI) displayed by the displaydevice (e.g., menu items and/or icons displayed on the display device)and navigated by the technician via a joystick or a set of four“up/down/left/right” buttons, as well as a “select/ok” button to takesome action pursuant to the selection of a menu item/icon. In furtherimplementations, the user interface may include a microphone and theprocessor may be configured to accept and process audible commands, suchthat docking station operations may be accomplished via voice-activatedcommands by simply speaking into the microphone.

Additionally, user interface 256 may include one or more indicators suchas, for example, LED indicators, audio devices, such as a speaker, abuzzer and/or an alarm, and combinations thereof. During normal usage ofthe docking station, the components of user interface 256 may be used todisplay, for example, the current status of the docking station, thecurrent status of the docked marking device, alerts and notificationsand option selections.

Timing system 260 may include an internal clock, such as a crystaloscillator device, for processor 266. Additionally, timing system 260may include a mechanism for registering time with a specified degree ofaccuracy, such as accuracy to the minute, second or millisecond. Timingsystem 260 may also include a mechanism for registering the calendardate. Using timing system 260, a timestamp may be appended to anyinformation that is handled by the docking station, such as for examplemarking device data, time of docking the marking device, time ofundocking the marking device, time of battery charging, and the like. Insome embodiments, timing system 260 may register the time and date usingits internal clock. In other embodiments, timing system 260 may receivetime and date information from location tracking system 262. In furtherembodiments, timing system 260 may receive time and date informationfrom an external timing system, such as a remote computer or network,via communication interface 254.

Location tracking system 262 may include any device that can determinegeographical coordinates to a specified degree of accuracy. For example,location tracking system 262 may include a Global Positioning System(GPS) receiver or a Global Navigation Satellite System (GNSS) receiver.A GPS receiver may provide, for example, any standard format datastream, such as a National Marine Electronics Association (NMEA) datastream. The location tracking system 262 may include an error correctioncomponent which may be a mechanism for improving the accuracy of thegeographical coordinates provided by the location tracking system 262.In one example, the error correction component may include an algorithmfor correcting offsets, such as due to local disturbances in theatmosphere, in the geographical coordinates provided by locationtracking system 262. Using location tracking system 262, geographicalcoordinates can be recorded and/or transmitted for any docking stationoperation or information.

In another embodiment, location tracking system 262 may include a deviceor mechanism that determines location such as by performingtriangulation by the use of cellular telephone towers.

ID reader 264 includes a mechanism for short range identification of theID tag 265 which may be affixed to the marking device. ID reader 264 maybe a radio frequency identification (RFID) reader for reading an RFIDtag affixed to the marking device. In another embodiment, ID reader 264may include a barcode reader for reading a barcode tag affixed to themarking device. The ID reader 264 typically reads the ID tag 265 whenthe marking device is docked in the docking station.

Processor 266 may be any general purpose processor, controller ormicrocontroller device that is capable of managing the overalloperations of the docking station as described herein. The processor 266may include a single processing device or more than one processingdevice.

Memory 270 may comprise any computer-readable media and may storecomputer instructions for implementing the various functions describedherein as well as any data associated with operation of the dockingstation. The processor 266 may be used to execute the storedinstructions. Memory 270 may include volatile and/or non-volatile datastorage media and/or data storage devices. For example, memory 270 maybe, but is not limited to, a random access memory (RAM), a read-onlymemory (ROM) and/or a removable memory device, such as a USB flashmemory.

As indicated above, communication control module 280 includes softwarefor controlling communication interface 252 to communicate with themarking device and for controlling communication interface 254 tocommunicate with a local or remote computing device. The communicationmay be associated with any function of the docking station, includingbut not limited to data transfer, control of the marking device, batterycharging, diagnostics and calibration, for example. As indicated above,the communication with the marking device may be by wired connection ormay be wireless. Further, the communication with the computing devicemay be by wired connection or may be wireless.

Data transfer module 282 controls data transfer to and between themarking device, the docking station and the local or remote computingdevice. Marking device data may be transferred from the marking deviceto data storage 290 in memory 270 for later transfer to the computerdevice. In other embodiments, data transfer module 282 is configured tocontrol data transfer between the marking device and the computingdevice without temporary storage in data storage 290. In furtherembodiments, data transfer module 282 is configured to control datatransfer from the docking station to the marking device. The data may betransferred to the marking device from data storage 290 and/or from thecomputing device. By way of example only, the data transferred to themarking device may define some or all parameters of a marking operationto be performed by the marking device.

In some embodiments, data transfer module 282 may be configured toprovide data backup for the marking device. By copying marking devicedata to the local memory in the docking station and/or to the local orremote computing device at specified times, data integrity and datasecurity are provided, even if the marking device is damaged, lost orstolen. For example, data can be copied from the marking device to thedocking station upon completion of a marking operation or a partthereof, or at specified intervals.

Data transfer module 282 may ensure synchronization of data between themarking device and data storage 290 as described below. Data transfermodule 282 may perform functions such as format conversion, datacompression and the like, related to data communication. In someembodiments, data storage 290 may be a removable memory component, suchas a USB flash memory, that is physically removed from the dockingstation and installed in the local or remote computing device for datatransfer.

Battery control module 284 may control monitoring and charging of one ormore batteries in the marking device by battery control circuit 272. Thebattery control module 284 may determine the charge state of the one ormore batteries in the marking device and, if necessary, initiate andcontrol battery charging. The battery control module, in conjunctionwith timing system 260, may be configured to record a date and time ofbattery charging. The battery control module 284, in conjunction withlocation tracking system 262, may be configured to record geographicalcoordinates of the battery charging operation. The battery controlmodule 284 may be configured to determine and/or record variousparameters of the one or more batteries in the marking device, includingbut not limited to battery quality and/or battery capacity.

Diagnostics module 286 may be configured to perform diagnostics of themarking device. In particular, diagnostics module 286 may place themarking device in a diagnostics mode and may execute a diagnosticsroutine on the marking device. The diagnostics routine may includesending stimulus signals to the marking device and receiving responsesor lack thereof which indicate the operational state of the markingdevice. The diagnostics routine may test some or all of the componentsof the marking device.

Diagnostics module 286 may also perform calibration of one or morecomponents of the marking device. For example, when a component of themarking device provides a response that does not meet specification, thecomponent may be adjusted by appropriate signals sent by the diagnosticsmodule 286 to meet specification.

Diagnostics module 286 may also be configured to performself-diagnostics of the docking station. In this case, diagnosticsmodule 286 may place the docking station in a diagnostics mode and mayexecute a diagnostics routine for testing some or all components of thedocking station. The result of the diagnostics routine can be recordedand/or transmitted to the local or remote computing device.

The diagnostics module 286, in conjunction with timing system 260, maybe configured to record a time and date when a diagnostics and/orcalibration routine was performed. Diagnostics module 286, inconjunction with location tracking system 262, may be configured torecord the geographical coordinates where a diagnostics and/orcalibration routine was performed. The recording of diagnosticsinformation may be important in establishing that the marking deviceand/or the docking station was functioning properly at a particular timeand date and/or location.

Security module 288 may be configured to control various securitycomponents and functions of the docking station. In some embodiments,security module 288 may be configured to receive the ID of the markingdevice from ID reader 264 and compare the ID of the marking device witha list of approved marking device IDs. If the ID of the marking devicedoes not match one of the approved marking device IDs in the list,operation of the docking station may be modified and/or terminated. Forexample, an alert can be generated by the docking station and/or analert can be transmitted to the local or remote computing device.Furthermore, operations such as data transfer, battery charging and thelike can be terminated when the ID of the marking device does not matchan approved marking device ID.

In other embodiments, security module 288 may be configured to receive auser ID from user interface 256, such as via a keypad or other inputdevice, and compare the user ID with a list of approved user IDs. In theabsence of a match between the user ID and one of the approved user IDs,operation of the docking station can be modified or terminated and analert can be generated as described above.

In further embodiments, security module 288 may be configured to controla locking mechanism, such as a safety strap, a locking bar or otherlocking device. The locking mechanism may secure the marking device ormay secure an enclosure for the marking device, such as for example aweatherproof enclosure. Thus, for example, security module 288 may beconfigured to maintain the locking mechanism in a locked state if theuser ID does not match one of the approved user IDs. In furtherembodiments, security module 288 may be configured, in conjunction withtiming system 260, to maintain the locking mechanism in a locked stateat specified times and dates, such as, for example, during nighttime,weekends and holidays. In further embodiments, security module 288 maybe configured, in conjunction with location tracking system 262, tomaintain the locking mechanism in a locked state when the dockingstation is outside specified geographical coordinates, is at specifiedgeographical coordinates, or is within specified geographicalcoordinates. The specified geographical coordinates may indicate alocation or area where removal of the marking device from the dockingstation is not permitted.

In further embodiments, the security module 288 may be configured togenerate a user alert or notification when a marking device is notpresent in the docking station. Presence or lack of presence of themarking device may be detected, for example, by a sensor switch. Inother embodiments, the security module 288 may be configured to generatea user notification or alert when the marking device is present in thedocking station but is not secured in the docking station, for example,the marking device is not properly positioned or the locking mechanismis not engaged. In further embodiments, security module 288 may beconfigured to respond to a security command from a local or remotecomputing device. The security command may cause the security module 288to terminate operations, to engage any locking mechanism and/or to shutdown, for example.

It will be understood that the above described components and functionsof the docking station may be utilized separately or in any combination.Furthermore, various components of the docking control electronics 250shown in FIG. 4 and described above may be omitted from the dockingstation, within the scope of the invention. As noted above, batterycharging may be a separate function not included in the docking station.The docking station, for example, may not include ID reader 264, timingsystem 260 and/or location tracking system 262 in particularapplications and configurations. In some embodiments, the dockingstation may be controlled by the computing device, in which case, all orpart of user interface 256 may be omitted. Depending on theconfiguration, various software modules may be omitted, and in otherembodiments, additional software modules may be included in the dockingstation. As described above, some embodiments of the docking station mayinclude minimal or no electronics, in which case the docking stationserves as a holder for the marking device.

FIGS. 5A and 5B are top and side views, respectively, of a portion ofdocking station 100. FIGS. 5A and 5B illustrate that cradle 118 isrecessed into the upper end of support housing 114. Additionally, afemale alignment feature 310 is provided within cradle 118 and isrecessed into support housing 114. Male connector pins 314 are arrangedwithin female alignment feature 310, to which electrical signals andpower are connected. The number, type, and arrangement of male connectorpins 314 may vary according to the requirements of docking station 100and/or the marking device 150 to be docked. Similarly, the dimensions ofcradle 118 and female alignment feature 310 may vary according to therequirements of docking station 100 and/or the marking device 150 to bedocked.

FIGS. 6A and 6B are side and bottom views, respectively, of a portion ofmarking device 150. FIG. 7 is a side view of marking device 150 beingattached to docking station 100. Docking station interface 174 ofmarking device 150 is designed to fit into cradle 118 of docking station100. Accordingly, FIGS. 6A and 6B show that the geometry of dockingstation interface 174 is complementary to the geometry of cradle 118 ofFIGS. 5A and 5B. For example, the body of docking station interface 174is designed to fit within the recessed area of cradle 118. Further, amale alignment feature 410 is integrated into docking station interface174. Male alignment feature 410 is designed to fit within the recessedfemale alignment feature 310 of cradle 118 shown in FIGS. 5A and 5B. Aset of female connector pins 414 are arranged within male alignmentfeature 410, to which electrical signals and power are connected. Thenumber, type, and arrangement of female connector pins 414 may varyaccording to the requirements of marking device 150 and docking station100. Female connector pins 414 of marking device 150 are arranged tosubstantially align with the arrangement of male connector pins 314 ofdocking station 100. As a result, when marking device 150 is attached todocking station 100, male connector pins 314 fit into female connectorpins 414 of marking device 150, providing an electrical connectiontherebetween, as shown in FIG. 7.

While FIGS. 5A, 5B, 6A, and 6B describe a pin and hole type ofconnection (e.g., male connector pins 314 fitting into female connectorpins 414) between docking station 100 and marking device 150, thisconnection is exemplary. Those skilled in the art will recognize thatany type of electrical connection mechanism may be used, such as, butnot limited to, an induction coupling mechanism. In addition, themechanical and electrical coupling between docking station 100 andmarking device 150 can be at any convenient location on the two devices,with complementary elements on the two devices to facilitate couplingand decoupling. Furthermore, the mechanical and electrical couplingelements can be combined, as shown in FIGS. 5A, 5B, 6A, 6B and 7, or canbe separate coupling elements.

As illustrated in FIG. 7, docking station interface 174 of markingdevice 150 fits into cradle 118 of docking station 100. In particular,male alignment feature 410 of docking station interface 174 havingfemale connector pins 414 is aligned with and fit into female alignmentfeature 310 of cradle 118 that has male connector pins 314.

FIG. 8A is a top view of an exemplary configuration incorporatingdocking station 100. More specifically, FIG. 8A is a top view of aconfiguration incorporating docking station 100 in a vehicle cab 600 ofthe type typically used in the field. Vehicle cab 600 may include both adriver seat 610 and a passenger seat 614, which are facing a dash 618.In this mounting configuration, docking station 100 may be mounted tothe back wall of vehicle cab 600 (i.e., the wall opposite dash 618) in alocation that is substantially centralized between driver seat 610 andpassenger seat 614 for ease of access. For example, docking station 100may be secured to the back wall of vehicle cab 600 by use of securityscrews to prevent the unauthorized removal of docking station 100.Docking station 100 is positioned to face the front (i.e., toward dash618) of vehicle cab 600 to allow for easy attachment and removal ofmarking device 150.

Docking station 100 may be wired directly into a vehicle's power system.Docking station 100 thus receives power simultaneously with othervehicle components (when the key is in the accessory, power, start, orrun position), and powers down upon vehicle power off. In oneembodiment, the design and construction of docking station 100 providesa power line and a ground line. Both lines may be spliced into, forexample, a restraint control module 622 that is typically locateddirectly under passenger seat 614 of the vehicle. As a result, dockingstation 100 receives power when restraint control module 622 receivespower. Docking station 100 provides a battery charging mechanism formarking device 150 via the combination of the vehicle power and dockingcontrol electronics 128. In another embodiment, the docking station maycharge the marking device at any time (including accessory, power,start, run or off positions), for example, at preset times before thebeginning of a shift to ensure that the marking device is fully charged,or for a period of time after the vehicle is shut off at the end of ashift.

Additionally, FIG. 8A shows an onboard computer 626 within vehicle cab600. Onboard computer 626 may be any computing device, such as, but notlimited to, any laptop computer, handheld computer or onboard serverthat is capable of executing software applications related to operationsof docking station 100 and marking device 150. In particular, there maybe a wired connection, such as wired connection 140, between dockingstation 100 and onboard computer 626. In an embodiment, onboard computer626 communicates with marking device 150 via a wireless communicationlink when within range. Also, when marking device 150 is attached todocking station 100, docking station 100 provides a wired communicationslink between onboard computer 626 and marking device 150. The type ofinformation that may be exchanged between onboard computer 626 andmarking device 150 may include, but is not limited to, marking data,timing data, GPS data, RFID data, status data, health data, software,and firmware updates, diagnostics information, and the like.

FIG. 8B is a top view of another embodiment incorporating dockingstation 100. In this mounting configuration, docking station 100 may besecurely fastened to the floor of vehicle cab 600 in place of apassenger seat. In an embodiment, docking station 100 is securely boltedto the floor of vehicle cab 600 using, for example, a set of existingpassenger seat bolt holes 630 in the floor of vehicle cab 600.Optionally, a mounting plate 634 may be provided at base 110 of dockingstation 100 for bolting to bolt holes 630. As depicted in FIG. 8B, apassenger seat is not present and restraint control module 622 may belocated underneath the cab floor covering. As previously discussed, thepower line and ground lines of docking station 100 may be spliced intorestraint control module 622. Additionally, a USB or similar connectionmay be provided between docking station 100 and onboard computer 626.This mounting configuration allows docking station 100 to be installedwithout drilling additional holes in the floor of vehicle cab 600. As aresult, docking station 100 is positioned in place of the passenger seatand may be oriented to allow easy access through the passenger door ofvehicle cab 600.

FIGS. 8A and 8B illustrate embodiments where the docking station ismounted within a vehicle cab. It will be understood that the dockingstation can be mounted in any convenient location in a vehicle. Forexample, docking station may be mounted in the bed of a truck, in therear of a van, within a panel truck or trailer, or in any other desiredlocation. Further, the docking station can retain the marking device inany desired orientation, such as vertical, horizontal or any otherdesired orientation. In addition, any number of docking stations can bemounted in a vehicle.

In some embodiments, the docking station may include a weatherproofenclosure for the marking device. The weatherproof enclosure may bebeneficial, for example, when the docking station is exposed to theweather, such as in the bed of a truck. The weatherproof enclosure mayalso provide enhanced security and may include a locking mechanism.

FIG. 8C is a functional block diagram of a network system 650 thatincludes the mobile docking station 100. More specifically, networksystem 650 includes one or more mobile docking stations 100 and one ormore associated marking devices 150. Each mobile docking station 100 ofnetwork system 650 may be connected to onboard computer 626 of thevehicle in which it is installed, as shown in FIGS. 8A and 8B. Inanother embodiment, onboard computer 626 may be any on-site computer,and is not limited to a computer in a vehicle. Additionally, eachonboard computer 626 or other on-site computer of network system 650 maybe connected to a remote computing device, such as remote computer 654.Remote computer 654 may be a centralized computer, such as a centralserver of, for example, the locate service provider.

In order to facilitate the network connection, each onboard computer 626or other on-site computer includes a communication link 658. Likewise,remote computer 654 includes a communication link 662. Communicationlink 658 and communication link 662 may be any wired and/or wirelesscommunication interface by which information may be exchanged. Examplesof wired communication interfaces may include, but are not limited to,USB ports, RS232 connectors, RJ45 connectors, Ethernet, and anycombinations thereof. Examples of wireless communication interfaces mayinclude, but are not limited to, an Intranet connection, Internet,Bluetooth® technology, Wi-Fi, Wi-Max, IEEE 802.11 technology, radiofrequency (RF), Infrared Data Association (IrDA) compatible protocols,Local Area Networks (LAN), Wide Area Networks (WAN), Shared WirelessAccess Protocol (SWAP), combination thereof, and other types of wirelessnetworking protocols. The wireless interface may be capable of capturingsignals that reflect a user's intent. For example, the wirelessinterface may include a microphone that can capture a user's intent bycapturing the user's audible commands. The wireless interface may alsointeract with a device that monitors a condition of the user, such aseye movement, brain activity, and/or heart rate.

FIG. 9 is a flow diagram of a method 700 of using a docking stationaccording to embodiments of the invention. In particular, FIG. 9 is aflow diagram of method 700 of synchronizing the data of, for example,marking device 150 with a local or remote computer, such as onboardcomputer 626, when detected in docking station 100. Method 700 mayinclude, but is not limited to, the following acts, which are notlimited to any order.

In act 710, the docking station receives power. For example, whendocking station 100 is installed in a vehicle, as shown in FIGS. 8A and8B, docking station 100 receives direct current (DC) power when thevehicle key is in the accessory, power, start, or run position.

In act 714, it is determined whether a marking device 150 is present inthe docking station 100. For example, using software of onboard computer626, queries of docking station 100 may be performed in order todetermine the presence or absence of marking device 150. In oneembodiment, onboard computer 626 may query the RFID reader of dockingstation 100 in order to determine whether RFID data is returned. Morespecifically, when marking device 150 is present in docking station 100,RFID data is returned from its RFID tag 178 to onboard computer 626 bythe RFID reader 129 of docking station 100. By contrast, when markingdevice 150 is not present in docking station 100, no RFID data isreturned to onboard computer 626 from docking station 100.

In another example, a logic state may be returned from docking controlelectronics 128, depending upon whether an electrical connection existsbetween docking station 100 and marking device 150 (e.g., between maleconnector pins 314 of docking station 100 and female connector pins 414of marking device 150). This may be referred to as “docking pinawareness.” Other methods of determining whether a marking device ispresent in the docking station are possible, such as pressure sensorsand any number of other solutions. If it is determined that markingdevice 150 is present in docking station 100, method 700 proceeds to act718. If it is determined that marking device 150 is not present indocking station 100, method 700 ends.

In act 718, it is determined whether a data synchronization operation isneeded between the marking device and the local or remote computer. Datasynchronization is the process by which the local or remote computerreceives data that was not previously exchanged between the markingdevice and the local or remote computer. For example, using software ofonboard computer 626, it may be determined whether a datasynchronization operation is needed between marking device 150 andonboard computer 626. For example, onboard computer 626 interrogates thedata (e.g., marking data, timing data, GPS data, RFID data, and thelike) that may be stored on marking device 150 and checks a flag, suchas a send/acknowledge flag, to determine whether a packet of data wastransmitted and received successfully. When the expected flags arepresent, onboard computer 626 skips over that packet of data in order toavoid collecting duplicate data. Any data that was not successfullytransmitted and/or received is transmitted from marking device 150 toonboard computer 626 (or remote computer via wireless communication) viathe USB or similar connection between docking station 100 and onboardcomputer 626. If it is determined that a data synchronization operationis needed, method 700 proceeds to act 722. If it is determined that adata synchronization operation is not needed, method 700 ends.

In act 722, a data synchronization operation is performed between themarking device 100 and the remote or local computer. For example, a datasynchronization operation is performed between marking device 150 andonboard computer 626 via the USB connection between docking station 100and onboard computer 626. Once the data is synchronized, method 700ends.

Referring again to method 700 of FIG. 9, docking station 100communicates with onboard computer 626 and, if appropriate, may beginsynchronizing data immediately when marking device 150 is detected indocking station 100. Alternatively, a manual control 134, such as the“initiate data synchronization” push button of docking station 100allows the operator to manually perform synchronization at any time.Also, data synchronization may occur automatically upon the docking ofthe marking device.

A data synchronization operation is described above in connection withFIG. 9. It will be understood that communication between docking station100 and marking device 150 may include any control and/or data transferfunction, including but not limited to issuing commands to markingdevice 150, receiving status and other operating information frommarking device 150, downloading ticket information and other operatingparameters, uploading information of any type, performing diagnostics,and the like.

FIG. 10 is a flow diagram of another method of using a docking station.In particular, FIG. 10 is a flow diagram of a method 800 of managing theindicators and/or manual controls of docking station 100 when a markingdevice, such as marking device 150, is detected therein. Method 800informs the user of status changes and other conditions that may requireattention. Method 800 may include, but is not limited to, the followingacts, which are not limited to the following order.

In act 810, the docking station receives power. For example, whendocking station 100 is installed in a vehicle, as shown in FIGS. 8A and8B, docking station 100 receives DC power when the vehicle key is in theaccessory, power, start, or run position.

In act 814, it is determined whether a marking device is present in thedocking station. For example, if it is determined that marking device150 is not present in docking station 100, method 800 proceeds to act818. If it is determined that marking device 150 is present in dockingstation 100, method 800 proceeds to act 822. The presence or absence ofmarking device 150 in docking station 100 may be determined as describedabove in connection with FIG. 9.

In act 818, indicators 130 are set to show that no marking device ispresent and certain manual controls are disabled. For example, a redbattery status indicator and a red synchronization status indicator maybe turned on, and the initiate data synchronization push button may bedeactivated.

In act 822, it is determined whether the power source, for example, abattery, of marking device 150 needs charging. For example, onboardcomputer 626 interrogates control electronics 170 of marking device 150in order to determine the health status of rechargeable batteries 172.If it is determined that rechargeable batteries 172 of marking device150 do not need charging, method 800 proceeds to act 826. If it isdetermined that rechargeable batteries 172 of marking device 150 do needcharging, method 800 proceeds to act 830.

In act 826, an indicator 130 is set to show battery status=charged. Forexample, a green battery status indicator may be turned on. Method 800proceeds to act 834.

In act 830, an indicator 130 is set to show battery status=charging. Forexample, a yellow battery status indicator may be turned on and causedto blink. Alternatively, in the case of total battery failure, a redbattery failure indicator may be turned on in order to show a defectivebattery in marking device 150.

In act 834, it is determined whether a data synchronization operation isneeded between the marking device and the local or remote computer. Forexample, if it is determined that a data synchronization operation isneeded, method 800 proceeds to act 838. However, if it is determinedthat a data synchronization operation is not needed, method 800 proceedsto act 850. The need for a synchronization operation may be determinedas described above in connection with FIG. 9.

In act 838, an indicator 130 is set to show synchronization is inprogress. For example, an orange synchronization status indicator may beturned on and caused to blink. In act 842, it is determined whether adata synchronization error condition is present. For example, onboardcomputer 626 determines whether a data synchronization error conditionhas been identified. If a data synchronization error condition is notpresent, method 800 returns to act 838. If a data synchronization errorcondition is present, method 800 proceeds to act 846.

In act 846, an indicator 130 is set to show whether a datasynchronization error condition is present. For example, a redsynchronization error indicator may be turned on and caused to blink. Inact 850, it is determined whether the initiate data synchronization pushbutton of docking station 100 has been pushed. For example, onboardcomputer 626 interrogates docking control electronics 128 of dockingstation 100 to determine the status thereof. If it is determined thatthe initiate data synchronization push button has been pushed, method800 proceeds to act 838. If it is determined that the initiate datasynchronization push button has not been pushed, method 800 thenproceeds to act 854.

In act 854, an indicator 130 is deactivated. For example, the orangesynchronization status indicator may be turned off.

FIG. 11 is a schematic diagram of a marking device attached to a dockingstation. In particular, FIG. 11 depicts a side view of marking device150 attached to docking station 100. Docking station 100 furtherincludes a locking mechanism 910. In addition to safety strap 142,marking device 150 may be lockable within a vehicle via the optionallocking mechanism 910 of FIG. 11. In one embodiment, locking mechanism910 may be a suitably rigid, strong, and tamperproof bracket (e.g.,hinged bracket) that is installed on support housing 114. Lockingmechanism 910 may include a switch or lever (not shown) to ensure thatmarking device 150 is properly secured within docking station 100 duringdriving (i.e., for safety) in the event of an accident, as well as toensure proper charging and data transfer. A keyed lock, such as apadlock, may be used to secure marking device 150 against theft.

FIG. 12 is a flow diagram of a method of using a docking station. Inparticular, FIG. 12 illustrates a method 1000 of notifying the user ofthe presence and security of the marking device in docking station 100.Method 1000 may provide an audible means of informing the user of thepresence and security of marking device 150 in docking station 100.Method 1000 may include, but is not limited to, the following acts,which are not limited to the following order.

In act 1010, it is determined whether docking station 100 is receivingpower. For example, when docking station 100 is installed in a vehicle,such as shown in FIGS. 8A and 8B, docking station 100 receives DC powerwhen the vehicle key is in the accessory, power, start, or run position.If onboard computer 626 determines that vehicle power is present, method1000 proceeds to act 1014. If onboard computer 626 determines thatvehicle power is not present, method 1000 ends.

In act 1014, it is determined whether a marking device 150 is presentwithin the docking station. For example, if it is determined thatmarking device 150 is not present in docking station 100, method 1000proceeds to act 1018. If it is determined that marking device 150 ispresent in docking station 100, method 1000 proceeds to act 1022. Thepresence or absence of marking device 150 in docking station 100 may bedetermined as described above in connection with FIG. 9.

In act 1018, an audible notification is generated to the user that themarking device 150 is absent from the docking station 100 within thevehicle. For example, a buzzer (via audio output 138 of docking station100) may be triggered until the vehicle is shut off or until markingdevice 150 is placed in docking station 100. Thus, it may be ensuredthat the user returns marking device 150 to the vehicle after each use.Method 1000 then returns to act 1014.

In act 1022, it is determined whether the marking device is securewithin the docking station 100. For example, onboard computer 626determines the status of safety strap 142 and/or the switch or lever oflocking mechanism 910 in order to determine whether such items are in asecure state. If it is determined that marking device 150 is secure indocking station 100, method 1000 ends. If it is determined that markingdevice 150 is not secure in docking station 100, method 1000 proceeds toact 1026.

In act 1026, an audible notification is generated, indicating to theuser that the marking device is not secure in docking station 100 withinthe vehicle. For example, a buzzer (via audio output 138 of dockingstation 100) may be triggered until the vehicle is shut off or untilmarking device 150 is placed in docking station 100. This ensures thatmarking device 150 is physically secure in the vehicle while the vehicleis moving. Method 1000 then returns to act 1022.

FIG. 13 is a schematic diagram of an exemplary configurationincorporating docking stations. In particular, FIG. 13 is a schematicdiagram of a bank of one or more docking stations 1100, which may befixed and suitable for use with at least one marking device. Forexample, FIG. 13 shows a home base facility 1110 at which a bank ofdocking stations 1100 are installed along a wall 1114. In anotherconfiguration, the bank of docking stations 1100 may be installed on thefloor or a table. Each docking station 1100 may be substantially thesame as docking station 100 as depicted in FIGS. 1 through 12, exceptthat its power source may be designed and constructed to utilize analternating current (AC) power source (e.g., an AC power source 1118),instead of the DC power of a vehicle. A shielded power cord terminatedin a three (3) prong plug may be used. The bank of docking stations 1100may also be powered by direct current (DC) power sources. Like dockingstation 100, each docking station 1100 allows a marking device, such asmarking device 150, to be attached and detached easily for charging and,where applicable, for data synchronization.

Each docking station 1100 is designed and constructed to be mountedagainst a fixed structure such as a wall. In addition, each dockingstation 1100 is designed and constructed of materials that preventunauthorized removal thereof. The bottom of each docking station 1100may be flat in order to allow for placement on the floor of a buildingor on a table. Each docking station 1100 may be affixed to the floorand/or wall using security screws to prevent the unauthorized removal ofthe docking station. A variety of attachment means may be used to affixdocking stations 1100. In addition, each docking station 1100 may bepositioned to allow the easy attachment and removal of a marking device.

Docking station 100 and where applicable, docking station 1100, maysupport the synchronization of the marking device to a local or remotecomputer, such as a remote computer 1122, which may be, for example, ahost server. This synchronization may be performed through the use of aUSB cable. Upon attachment of the marking device, each docking station1100 may determine whether or not data synchronization is necessary and,if it is, perform substantially the same data synchronization processthat is shown in method 700 of FIG. 9 and described above.

The status indicators and device controls of each docking station 1100may be substantially the same as those of docking station 100. A methodof managing the indicators and/or manual controls of each dockingstation 1100 may be substantially the same as method 800 of FIG. 10 fordocking station 100.

In another embodiment, each docking station 1100 may include a cleaningmechanism at the base thereof for cleaning any components that may beinstalled at the marking dispenser holder end of a marking device. Anexample of a cleaning mechanism may be a compact ultrasonic cleaningstation that utilizes cleaning fluid, such as, but not limited to,isopropyl alcohol.

FIGS. 14, 15, and 16 are perspective views of another embodiment of thedocking station according to the present invention. FIG. 14 depicts adocking station 1200 for docking a marking device 1250. Docking station1200 may be an example of another embodiment of both docking station 100and docking station 1100, which may be in a variety of locations infixed or mobile configurations.

In this embodiment of the docking station, docking station 1200 mayinclude a base 1210, a support housing 1214, and a cradle 1218. Thefunctions of base 1210, support housing 1214, and cradle 1218 aresubstantially the same as the functions of base 110, support housing114, and cradle 118, respectively, of FIGS. 1 through 13. Dockingstation 1200 of FIGS. 14, 15, and 16 differs primarily from dockingstation 100 and docking station 1100 of FIGS. 1 through 13 in itsphysical attributes.

In this embodiment of the docking station, marking device 1250 mayinclude a shaft 1254, a handle 1258, a marking dispenser holder 1262 anda docking station interface 1274. The functions of shaft 1254, handle1258, marking dispenser holder 1262, and docking station interface 1274are substantially the same as the functions of shaft 154, handle 158,marking dispenser holder 162 and docking station interface 174,respectively, of FIGS. 1 through 13. Marking device 1250 of FIGS. 14,15, and 16 differs primarily from marking device 150 of FIGS. 1 through13 in its physical attributes. In particular, in this embodiment,docking station interface 1274 is incorporated on the side of shaft 1254that is opposite handle 1258. By contrast and referring to FIG. 1,docking station interface 174 of marking device 150 is incorporated onthe same side of shaft 154 as handle 158.

With reference to FIGS. 14 and 16, respectively, marking device 1250 isshown separated from and attached to docking station 1200. FIG. 15 showsfurther details of docking station 1200. More specifically, FIG. 15shows an alignment feature 1222 of cradle 1218 that provides theelectrical and mechanical coupling to a corresponding alignment feature(not visible) of docking station interface 1274 of marking device 1250.

Additional security features may be incorporated into the dockingstations described herein (e.g., docking station 100, docking station1100 and docking station 1200). For example, in addition to the physicallocking mechanism, the docking stations may be equipped with a positiveidentification mechanism. This positive identification mechanism (notshown) is provided to ensure that the user is authorized to remove themarking device from the docking station. This mechanism may includebiometric, RFID, passcode, or any other means of positively identifyingthe user. For example, using intelligence that may be incorporated intodocking stations, in order to unlock the marking device, the user may beprompted to provide input that validates that he/she is authorized touse the marking device. In the event that the proper credentials aresupplied, the locking mechanism of the docking station releases themarking device to the user. If improper credentials are supplied, thedocking station may enter a security lockdown mode, trigger a remotealert to a supervisor of the user, and/or trigger an audible or visiblealarm indicating that it is not available for use.

In this embodiment, the docking stations may not allow the user toremove the marking device until positive identification, as explainedabove, has been provided. In this embodiment, the biometric, RFID,passcode or any other means shall be a feature of the docking stationsand provide enhanced security to the physical locking measures (e.g.,strap and padlock) already described.

In an embodiment and with regard to docking station 100, an audiblesecurity alarm may be tied into existing vehicle alarms, such as analarm that sounds when the key is left in the ignition when the useropens the door, when the lights are left on or when the user opens thedoor and so on. Alternatively, the vehicle may be disabled from startingif marking device 150 is not properly secured in docking station 100.

In another embodiment and with regard to docking stations 1100 and 1200,a supervisor of a user may view (e.g., using a graphical user interface(GUI) of remote computer 1122) the status of docking stations 1100 and1200, such as whether a marking device 150 is present and properlysecured or not.

The docking stations of the present invention (e.g., docking station100, docking station 1100, and docking station 1200) are not limited touse with a portable marking device. The docking stations may be suitablefor use with other types of portable devices. In an embodiment, thedocking stations described herein may accommodate and function with alocate device or similar instrument for detecting facilities. Moreover,the docking stations described herein may also accommodate and functionwith a combination marking and locate device.

FIG. 17 is a perspective view of a marking device docking station 1300that has processing and communications capability. Docking station 1300may be installed in, for example, a vehicle and is suitable for use inconjunction with a marking device, such as marking device 1350. In otherembodiments, docking station 1300 may be installed at a centralfacility, office or other fixed location. Thus, docking station 1300 maybe mobile or fixed. Docking station 1300 may serve as a home base forstorage of marking device 1350 and for charging the battery of markingdevice 1350. Marking device 1350 is, for example, an electronic markingdevice. In one example, marking device 1350 may be based on theelectronic marking devices that are described above in connection withmarking device 150.

Docking station 1300 may include a base 1310 and a body 1312.Additionally, a cradle 1314 is integrated into the upper end of body1312 (the end opposite base 1310). Cradle 1314 provides a means tomechanically and electrically couple marking device 1350 to dockingstation 1300. Base 1310, body 1312, and cradle 1314 may be made of anysuitably strong, rigid, and lightweight material, such as, but notlimited to, molded plastic and metal. Additionally, docking station 1300may include a security mechanism 1316 for holding and securing markingdevice 1350 into cradle 1314 in a lockable manner. For example, securitymechanism 1316 may be a flexible strap or a rigid bracket that may beplaced around the body of marking device 1350 and secured with a lockingmechanism (not shown) to docking station 1300.

Docking station 1300 may also include control electronics for providingprocessing and communications capability to docking station 1300. Forexample, docking station 1300 may include control electronics 1320 thatincludes a processing unit 1322, a local memory 1324, a communicationinterface 1326, a presence detection mechanism 1328, a securitydetection mechanism 1330, and, optionally, a location tracking system1332.

Processing unit 1322 may include any standard controller ormicroprocessor device that is capable of executing program instructions.Local memory 1324 may be any data storage mechanism for storing anyinformation that is processed locally at docking station 1300.Processing unit 1322 and local memory 1324 may be used for managing theoverall operations of docking station 1300.

Communication interface 1326 may include any wired and/or wirelesscommunication interface for connecting to a network (not shown) and bywhich information may be exchanged with other computing devices that maybe separate from docking station 1300 and/or with other docking stations1300. Examples of wired communication interfaces may include, but arenot limited to, USB ports, RS232 connectors, RJ45 connectors, Ethernet,and any combinations thereof. Examples of wireless communicationinterfaces may include, but are not limited to, an Intranet connection,Internet, Bluetooth® technology, Wi-Fi, Wi-Max, IEEE 802.11 technology,radio frequency (RF), Infrared Data Association (IrDA) compatibleprotocols, Local Area Networks (LAN), Wide Area Networks (WAN), SharedWireless Access Protocol (SWAP), any combinations thereof, and othertypes of wireless networking protocols.

Presence detection mechanism 1328 may include any mechanism of controlelectronics 1320 that is capable of determining whether a marking device1350 is present within cradle 1314. In one example, presence detectionmechanism 1328 may be a radio frequency identification (RFID) readerthat is able to read, for example, an RFID tag 1334 that is affixed tomarking device 1350. When marking device 1350 is present in cradle 1314,the RFID reader is able to read information (e.g., a marking device ID)from RFID tag 1334, which indicates that marking device 1350 is presentin docking station 1300. However, when marking device 1350 is notpresent in cradle 1314, the RFID reader is unable to read informationfrom RFID tag 1334, which indicates that marking device 1350 is notpresent in docking station 1300.

In another example, presence detection mechanism 1328 may includecircuitry for reading the state of a “presence signal,” which may be anelectronic signal that has one state (e.g., a logic high) when markingdevice 1350 is present and another state (e.g., a logic low) whenmarking device 1350 is not present. The “presence signal” may begenerated based, for example, upon sensing an electrical connection (ornot) between docking station 1300 and marking device 1350 at theinterface of cradle 1314.

Security detection mechanism 1330 may include any mechanism of controlelectronics 1320 that is capable of determining whether securitymechanism 1316 is engaged around marking device 1350 and locked. Forexample, presence detection mechanism 1328 may include circuitry forreading the state of a “locked signal,” which may be an electronicsignal that has one state (e.g., a logic high) when security mechanism1316 is engaged and locked and another state (e.g., a logic low) whensecurity mechanism 1316 is not engaged and locked.

In one example, the locking mechanism of security mechanism 1316 mayinclude an electromagnetic locking mechanism (not shown) that may beengaged/disengaged by a user of docking station 1300. In this example,the “locked signal” may be generated based upon sensing the state of theelectromagnetic locking mechanism. In another example, the lockingmechanism of security mechanism 1316 may include an electromechanicallocking mechanism (not shown) that may be engaged/disengaged by a userof docking station 1300. Again, the “locked signal” may be generatedbased upon sensing the state of the electromechanical locking mechanism.

Location tracking system 1332, which is optional in docking station1300, may include any device that can determine its geographicallocation to a specified degree of accuracy. For example, locationtracking system 1332 may include a global positioning system (GPS)receiver or a global navigation satellite system (GNSS) receiver. A GPSreceiver may provide, for example, any standard format data stream, suchas a National Marine Electronics Association (NMEA) data stream.Location tracking system 1332 may also include an error correctioncomponent (not shown), which may be any mechanism for improving theaccuracy of the geo-location data.

With respect to docking station 1300 being a recharging station for oneor more batteries (not shown) of marking device 1350, docking station1300 may include power management electronics 1340. When marking device1350 is present in docking station 1300, power management electronics1340 provides a standard battery charging function. Power managementelectronics 1340 is also able to communicate to control electronics 1320the charging state of the one or more batteries of marking device 1350,for example, 50% charged, 75% charged, and so on.

Optionally, receptacles may be integrated into base 1310 of dockingstation 1300 for accepting rechargeable batteries 1342, which may bespare rechargeable batteries for use in marking device 1350. In oneexample, FIG. 1 shows two receptacles for accepting two rechargeablebatteries 1342. When at least one rechargeable battery 1342 is presentin base 1310, power management electronics 1340 provides a standardbattery charging function. Power management electronics 1340 is alsoable to communicate to control electronics 1320 the presence of and thecharging state of any rechargeable batteries 1342.

In operation, under the control of processing unit 1322, any informationacquired and/or generated by docking station 1300 may be stored in localmemory 1324. For example, information about the presence and security ofmarking device 1350 at docking station 1300 may be logged in localmemory 1324. Information about the charging state of the one or morebatteries of marking device 1350 may be logged in local memory 1324.Information about the charging state of any rechargeable batteries 1342in base 1310 may be logged in local memory 1324. The geo-location datafrom location tracking system 1332 may be logged in local memory 1324,and the like.

Additionally, when marking device 1350 is present in docking station1300, any information about locate operations (hereafter called markingdata) that is stored in marking device 1350 may be transferred frommarking device 1350 to local memory 1324 of docking station 1300.

With respect to any of the aforementioned information, whetheroriginating from docking station 1300 or from marking device 1350,communication interface 1326 may be used to exchange information betweendocking station 1300 and any other computing devices that may beseparate from docking station 1300. Additionally, communicationinterface 1326 may be used to exchange information between dockingstation 1300 and any other docking stations 1300. Further, when, forexample, marking device 1350 is in use in the field (i.e., not docked),communication interface 1326 may be used to exchange informationwirelessly between docking station 1300 and marking device 1350. Dockingstation 1300 may communicate information regardless of whether a markingdevice 1350 is present. Examples of marking device docking stationconfigurations and networks are described with reference to FIGS. 18through 21.

FIG. 18 is a schematic diagram of a docking station network 1400, whichis one example of a docking station network. In this example, dockingstation network 1400 may include multiple fixed marking device dockingstations 1300 in communication with a central computing device.

In particular, FIG. 18 shows a bank of one or more docking stations1300, which may be fixed and suitable for use with at least one markingdevice 1350 at, for example, a home base facility. The bank of dockingstations 1300 may be floor-mounted along a wall 1410, as shown in FIG.18. In another configuration, the bank of docking stations 1300 may behung on a wall, free-standing on the floor, free-standing on a table,and any combinations thereof. In this configuration, the power sourcefor each docking station 1300 may be designed and constructed to utilizean alternating current (AC) power source (e.g., an AC power source1412). For example, a shielded power cord terminated in a three (3)prong plug may be used. The bank of docking stations 1300 may also bepowered by direct current (DC) power sources (not shown). Each dockingstation 1300 allows a marking device, such as marking device 1350, to beattached and detached easily for charging and, where applicable, fordata transfer.

In the configuration of docking station network 1400, the one or moredocking stations 1300 are in communication with a central computingdevice. The central computing device may be, for example, a centralcontrol panel 1414 and/or a central server 1416. Docking stations 1300may communicate with central control panel 1414 and/or central server1416 via their respective communication interfaces 1326. Further, thecommunication of each docking station 1300 may be managed by itsprocessing unit 1322. Central control panel 1414 and/or central server1416 may be used to collect information from docking stations 1300, suchas, but not limited to, marking device presence information, markingdevice security information, marking device battery status information,spare battery status information, marking data of marking devices, andthe like. The information returned from docking stations 1300 may beuseful, for example, for monitoring marking device inventory, monitoringmarking device battery status, monitoring marking device security,monitoring spare battery inventory and status, collecting marking data,and so on.

By way of example and referring again to FIG. 18, by using theprocessing and communications capabilities of docking stations 1300 athrough 1300 g, central control panel 1414 and/or central server 1416may determine, log, and report the following.

no marking device 1350 is present in docking station 1300 a, tworechargeable batteries 1342 are present in docking station 1300 a, thefirst rechargeable battery 1342 is 100% charged, the second rechargeablebattery 1342 is 100% charged;

no marking device 1350 is present in docking station 1300 b, norechargeable batteries 1342 are present in docking station 1300 b;

no marking device 1350 is present in docking station 1300 c, onerechargeable battery 1342 is present in docking station 1300 c, therechargeable battery 1342 is 78% charged;

a marking device 1350 d is present in docking station 1300 d, markingdevice 1350 d is locked down and secure, the batteries of marking device1350 d are 100% charged, two rechargeable batteries 1342 are present indocking station 1300 d, the first rechargeable battery 1342 is 100%charged, the second rechargeable battery 1342 is 100% charged;

a marking device 1350 e is present in docking station 1300 e, markingdevice 1350 e is locked down and secure, the batteries of marking device1350 e are 67% charged, two rechargeable batteries 1342 are present indocking station 1300 e, the first rechargeable battery 1342 is 82%charged, the second rechargeable battery 1342 is 74% charged;

no marking device 1350 is present in docking station 1300 f, norechargeable batteries 1342 are present in docking station 1300 f;

a marking device 1350 g is present in docking station 1300 g, markingdevice 1350 g is not locked down and secure, the batteries of markingdevice 1350 g are 100% charged, two rechargeable batteries 1342 arepresent in docking station 1300 g, the first rechargeable battery 1342is 100% charged, the second rechargeable battery 1342 is 94% charged;

three of a possible seven marking devices 1350 are present and accountedfor, two of the three present are fully charged, one of the threepresent is not fully charged; and

ten of a possible fourteen rechargeable batteries 1342 are present andaccounted for, five of the ten present are fully charged, five of theten present are not fully charged.

FIG. 19 is a schematic diagram of a docking station network 1500, whichis another example of a docking station network. In this example,docking station network 1500 may include multiple mobile marking devicedocking stations 1300 in the field and in communication with an onsitecomputing device. More specifically, FIG. 19 shows multiple vehicles1510, such as a vehicle 1510 a, 1510 b, and 1510 c. Installed in eachvehicle 1510 is a docking station 1300. For example, installed invehicles 1510 a, 1510 b, and 1510 c are docking stations 1300 a, 1300 b,and 1300 c, respectively. Vehicles 1510 a, 1510 b, and 1510 c may be,for example, the vehicles of locate technicians that are dispatched to ajobsite in the field. Docking stations 1300 a, 1300 b, and 1300 c areused to hold marking devices (not shown) in vehicles 1510 a, 1510 b, and1510 c. In this configuration, the power source for each docking station1300 may be designed and constructed to utilize the DC power of avehicle. Alternatively, instead of multiple docking stations 1300 inmultiple vehicles 1510, there may be multiple docking stations 1300 in aone vehicle 1510.

In the configuration of docking station network 1510, the one or moredocking stations 1300 are in communication with a central computingdevice. In one example, the central computing device may be an onsitecomputer 1520. Onsite computer 1520 may be any onsite computing device,such as, but not limited to, a laptop computer, a handheld computer, anda tablet device, that has network capability. In particular, onsitecomputer 1520 is capable of communicating with any docking stations 1300within its range. In one example, onsite computer 1520 may be present inone of the vehicles 1510.

As described with reference to FIG. 18, by using the processing andcommunications capabilities of docking stations 1300 a, 1300 b, and 1300c, onsite computer 1520 may determine, log, and report, for example,marking device presence, marking device battery status, marking devicesecurity, spare battery presence and status, marking data from eachmarking device, and so on.

FIG. 20 is a schematic diagram of a docking station network 1600, whichis yet another example of a docking station network. In this example,docking station network 1600 may include multiple mobile marking devicedocking stations 1300 in the field and in communication with each other.Docking station network 1600 is substantially the same as dockingstation network 1500 of FIG. 19, except that the multiple dockingstations 1300 are communicating directly with each other instead of to acentral computing device, such as onsite computer 1520 of FIG. 19.

With respect to docking station network 1600, any docking station 1300may poll any other docking station 1300 to determine their status (i.e.,peer-to-peer communication). This may be accomplished usingcommunication interface 1326 of each docking station 1300, which mayhave short range wireless communication capability, such as Bluetooth®.

The configuration of docking station network 1600 may be useful, forexample, to implement certain protocols with respect to performinglocate operations. In one example, a project ticket calls for two locatetechnicians. Therefore, two vehicles 1510 with two docking stations 1300(holding two marking devices), respectively, are present at the jobsite.In this example, a software rule may be implemented that once the locateoperation is complete, the marking devices 1350 must be present in therespective docking stations 1300 before any data from either markingdevice 1350 is processed and before the ticket can be classified ascomplete. In order to accomplish this, there is communication betweenthe two docking stations 1300 as to the presence of their respectivemarking devices 1350 and no data can be transferred until both arepresent. This may be useful to ensure a complete set of data toaccompany the completed project ticket (i.e., eliminating any chance ofpartial data). Further, this scenario may ensure the association of dataof the two marking devices involved. Any removal of either markingdevice in the middle of data transfer is communicated between the twodocking stations 1300, which will stop data transfer of the remainingmarking device.

FIG. 21 is a schematic diagram of a docking station network 1700, whichis still another example of a docking station network. In this example,docking station network 1700 may include at least one marking devicedocking station 1300 in communication with at least one marking device1350.

Docking station network 1700 is an example of using communicationinterface 1326 of docking station 1300 to exchange informationwirelessly with a marking device 1350. The configuration of dockingstation network 1700 may be useful, for example, to implement certainprotocols with respect to performing locate operations. In one example,docking station 1300 may receive a message from an external system via,for example, onsite computer 1520 of FIG. 19. This message is thenflashed from docking station 1300 to its associated marking device 1350.The user of marking device 1350 receives the message at his/her markingdevice 1350 and may respond accordingly.

In further embodiments, a docking station may be equipped with orotherwise communicatively coupled to a mobile/portable device (hereaftera “mobile device”), such as a cellular phone or personal digitalassistant (PDA), which are typically hand-sized or smaller. Such amobile/portable device provides processing, electronic storage,electronic display, user interface, communication facilities and/orother functionality for the docking station. Communicative coupling of amobile device with a docking station may allow the intelligence and/orvarious functionality of the mobile device to be used in place of, or inaddition to, an onboard processor and/or other onboard components (e.g.,such as those included in control electronics 128, 250 or 1320). Thedocking station communicatively coupled to a mobile/portable device maybe configured for docking of a marking device or for docking of acombination locate and marking device. The docking station may beconfigured for mechanical and/or electronic docking of locatingequipment.

More specifically, in some embodiments a mobile device may be employedto implement the various functionality discussed above in connectionwith the processor 266, the memory 270, the communication interfaces252, 254, the power source 274, the user interface 256, and in someinstances the timing system 260 and/or the location tracking system 262of an exemplary docking station. To this end, the mobile device itselfmay include one or more of a processor, memory, communication interface,power source, user interface, timing system and/or location trackingsystem (e.g., to facilitate GPS-enabled functionality). In someexemplary implementations, the mobile device may provide essentially allof the processing and related functionality required to operate thedocking station, while in other implementations the mobile device mayprovide only some portion of the overall functionality (e.g., aGPS-enabled mobile device may be employed primarily for obtaininggeo-location data, but not necessarily relied on substantively forprocessing power and/or memory).

In yet other implementations, the mobile device may provide redundant,shared and/or backup functionality for the docking station to enhancerobustness. For example, even though a docking station may include oneor more of a processor, memory, communication interface, power source,user interface, timing system and/or location tracking system, a mobiledevice communicatively coupled to or otherwise integrated with thedocking station may include one or more corresponding components toprovide redundant, shared and/or backup components and functionality.Examples of enhanced robustness provided by redundant components and/orfunctionality of a mobile device include, but are not limited to:providing for data comparison to establish data integrity (e.g.,validation of geo-location data by comparing data obtained by a locationtracking system in the docking station to geo-location data provided bya mobile device equipped with its own location tracking system);calibration of various parameters; power for various components (e.g., afirst power source of the docking station may be used to power/rechargea second power source of the mobile device, or vice versa); backupmemory storage; backup communication interfaces; support for multipledifferent communication protocols, communication channels, and/orcommunication media.

In various examples, a mobile device may be mechanically andelectronically coupled to a docking station via an appropriate mobiledevice cradle and/or connector, or otherwise integrated with orcommunicatively coupled to the docking station, so as to permit one ormore electronic signals to be communicated between the mobile device andthe docking station (e.g., one or more signals indicative of operationof the docking station may be supplied to the mobile device). In someimplementations, a mobile device cradle may be appropriately configuredsuch that one or more of a power connector and an I/O connector on themobile device engage with one or more complimentary connectors on themobile device cradle upon insertion/engagement of the mobile device inthe mobile device cradle. The one or more complimentary connectors onthe mobile device cradle in turn may be coupled to various signalsprovided by the docking station (e.g., to a docked marking device).Additionally, in some embodiments the mobile device cradle and/or thedocking station itself may include a battery pack and/or any other powersource for supplying power to and/or for assisting the battery of themobile device while the mobile device is connected to the dockingstation. In one example, the local power pack may be used to prolong thebattery life of the mobile device.

Various methods and apparatus for communicatively coupling mobiledevices to locating equipment in accordance with the present inventionmay allow different brands and/or types of mobile devices to bephysically secured to and/or electrically coupled to a docking station.In various implementations, a mobile device cradle integrated into adocking station may be mobile device-specific; i.e., the mobile devicecradle may be particularly configured such that the size and/orconnector positions are appropriate for a particular brand/model ofmobile device. Alternatively, a universal mobile device cradle with anadjustable size and/or adjustable connector locations (e.g., slidingconnectors along one or more sides of the cradle that may bemechanically locked in place) may be coupled to the docking station soas to accommodate a variety of different mobile devices. In otherexamples, a mobile device cradle may not require electrical connectionsintegrated therein, and one or more signals provided by the dockingstation may be communicated to the mobile device, and vice-versa, viaone or more wired connections (e.g., a cable or wire) or a wirelessconnection (e.g., a Bluetooth® connection). In yet other examples, themobile device need not be physically secured to the docking station, butmay be communicatively coupled to the docking station via one or morewired and/or wireless connections.

FIGS. 22A through 22D are perspective views of examples of mobiledevice-specific cradles 1612-1618 that may be integrated with (e.g.,installed on) a docking station according to some embodiments. Forpurposes of the following discussion, docking station 1200 isillustrated in the figures as an exemplary docking station with whichthe mobile/portable device may be coupled/integrated. However, it shouldbe appreciated that the concepts discussed below apply similarly toother docking stations. Furthermore, as noted above, it should beappreciated that in some implementations various components and/orfunctionality of the control electronics of the docking station may beprovided, in whole or in part, by the mobile device engaged in thecradles 1612-1618.

Device-specific cradles 1612-1618 may each be configured for holding aparticular type of mobile device. The mobile device may be any mobiledevice that has at least a processing unit and a communicationinterface, and preferably a user interface mechanism. Examples of mobiledevices include, but are not limited to, any of a wide variety of mobilephones, personal digital assistants (PDA), and/or any other personalcommunication and/or media devices, such as the iPod® Touch device.

In FIGS. 22A through 22D, each device-specific cradle may be associatedwith a certain brand and/or style of mobile device. For example,device-specific cradle 1612 of FIG. 22A may be configured for holding acertain type of mobile device 1630; device-specific cradle 1614 of FIG.22B may be configured for holding a different type of mobile device1632; and device-specific cradle 1616 of FIG. 22C may be configured forholding yet another type of mobile device 1634. Once a mobile device isinserted in its corresponding device-specific cradle on the dockingstation, its processing capabilities, user interface capabilities,communication capabilities, data storage capabilities, and/or any othercapabilities may be used in combination with components of the dockingstation to perform various functions discussed elsewhere herein.

Each device-specific cradle may be electrically coupled to one or morecomponents of the docking station. To this end, each device-specificcradle may include an input/output (I/O) connector for electricallyconnecting to its corresponding mobile device when the mobile device issecured within its device-specific cradle. Alternatively, a wirelesscommunication link may be provided between the docking station and themobile device that is secured within its device-specific cradle.

FIGS. 23A and 23B are perspective views of an example of a mobile deviceuniversal cradle 1640 that may be integrated with (e.g., installed on) adocking station. Universal cradle 1640 may include adjustable elements1642 that allow substantially any size, brand, and/or style of mobiledevice to be secured therein. Because the locations and types of I/Oconnectors on mobile devices may differ from one brand and/or style ofmobile device to another, in one aspect a docking station having auniversal cradle 1640 may utilize a cable, such as cable 1650, tofacilitate the electrical connection between the docking station and themobile device. The cable may be configured to provide an electricalconnection between an I/O connector type of the docking station and adevice-specific I/O connector type of the mobile device. In one example,cable 1650 may include a standard universal serial bus (USB) connectorat one end for connecting the cable 1650 to the docking station and adevice-specific connector at the opposite end for connecting the cable1650 to mobile device 1652.

FIG. 23A shows an empty universal cradle 1640, without a mobile devicesecured therein. FIG. 23B shows universal cradle 1640 with a mobiledevice (e.g., mobile device 1652) secured therein by, for example,adjustable elements 1642 being squeezed against the sides of mobiledevice 1652. FIG. 23B also shows cable 1650 plugged into mobile device1652, such that the docking station and the mobile device 1652 areelectrically connected.

Again, once a mobile device is installed in universal cradle 1640 on thedocking station, its processing capabilities, user interfacecapabilities, communication capabilities, data storage capabilities,and/or any other capabilities may be used in combination with componentsof the docking station to perform various functions discussed elsewhereherein. As noted above, the mobile device may provide essentially all ofthe processing and related functionality required to operate the dockingstation, or may provide only a portion of the overall functionality.Also, the mobile device may provide redundant, shared and/or backupfunctionality for the docking station to enhance robustness.

In some embodiments, any mobile device-specific cradles and/or universalcradles provided in connection with the docking station may beremovable, replaceable and/or exchangeable. For example, the mobiledevice-specific cradles 1612-1618 and/or universal cradle 1640 may beremoved from the docking station and then reattached as desired.

In other embodiments, a mobile device may be connected to a dockingstation through mechanisms requiring less external hardware to beattached to the docking station. For example, FIGS. 24A and 24B areperspective views of a slot, pocket, and/or pouch in a docking stationfor holding mobile devices. In one example, FIG. 24A shows a slot 1670integrated into docking station 1200 into which a mobile device, such asmobile device 1672, may be inserted. An electrical connection (notshown) may be integrated into a portion of slot 1670 (e.g., along one ormore sides and/or the bottom of slot 1670) for connecting to mobiledevice 1672.

In another example, FIG. 24B shows a holder 1680 that is secured, forexample, to the side of the docking station 1200. A mobile device, suchas mobile device 1672, may be inserted into holder 1680. Holder 1680 maybe ruggedized for protection of mobile device 1672 and/or may besealable for weatherproof operation. A cable (not shown), such as cable1650 of FIGS. 23A and 23B, may pass through the walls or through theseal of holder 1680 for providing an electrical connection between thedocking station 1200 and mobile device 1672.

When a cable, such as cable 1650, is to be used to facilitate aconnection between a mobile device and a docking station, as shown forexample in FIGS. 23A, 23B and 24B, the cable may be configured toprovide a connection between the I/O connector type of the dockingstation and the device-specific I/O connector type of the mobile device.For example, the cable may be in the form of a phone adaptor, with oneend configured to connect to the I/O connector of the docking station,and the other end configured to connect to the I/O connector of aspecific type of mobile device. FIG. 25 illustrates perspective views ofexamples of device-specific phone adaptors 1710 for use in facilitatingwired communication with a docking station.

Docking station 1200 may include a standard I/O connector 1720 intowhich any phone adaptor 1710 may be plugged. For example, each phoneadaptor 1710, such as phone adaptor 1722, 1724, or 1726, may include astandard I/O connector 1730 that is the counterpart to I/O connector1720 of the docking station. For example, if I/O connector 1720 of thedocking station is a male I/O connector, I/O connector 1730 of phoneadaptor 1710 can be a corresponding female I/O connector. Conversely, ifI/O connector 1720 of the docking station is a female I/O connector, I/Oconnector 1730 of phone adaptor 1710 can be a corresponding male I/Oconnector.

In a specific example, phone adaptor 1710 may be a USB-based adaptor;i.e., I/O connector 1720 on the docking station, may be a standard USBport and I/O connector 1730 of phone adaptor 1710 may be a USBconnector.

At the other end of phone adaptor 1710, an I/O connector may beconfigured to connect with a certain type of mobile device. For example,phone adaptor 1722 may include a device-specific I/O connector 1740 forconnecting to a certain brand and/or style of mobile device (not shown).Phone adaptor 1724 may include a device-specific I/O connector 1742 forconnecting to a different brand and/or style of mobile device (notshown). Phone adaptor 1726 may include a device-specific I/O connector1744 for connecting to a yet another brand and/or style of mobile device(not shown).

Alternatively, wired communication may be complemented or replaced withany of various forms of wireless communication between a mobile deviceand a docking station. For example, FIG. 26 illustrates a user-wornmobile device 1760 that is in communication with docking station 1200.The docking station 1200 may include a communication interface 1762,which may be any wired and/or wireless communication interface, asdescribed above. FIG. 26 also shows a locate technician 1770 having abelt-worn mobile device, such as mobile device 1760. That is, mobiledevice 1760 may be installed in a standard belt-worn holster. In thisexample, mobile device 1760 may communicate with the docking stationvia, for example, Wi-Fi communication, such as Bluetooth® communication.In various implementations, the control electronics of the dockingstation may or may not include processor, memory and/or user-interfacecomponents; if any of these are included, similar components of themobile device 1760 nonetheless may provide advantageous redundancy(e.g., for convenience of the technician 1770).

Any mobile device used in connection with a docking station, andoptionally the docking station itself, may include a communicationinterface. For example, the communication interfaces of the mobiledevice and the docking station may be any wired and/or wirelesscommunication interface by which information may be exchanged. Examplesof wired communication interfaces may include, but are not limited to,USB ports, RS232 connectors, RJ45 connectors, Ethernet, and anycombinations thereof. Examples of wireless communication interfaces mayinclude, but are not limited to, an Intranet connection, Internet,Bluetooth® technology, Wi-Fi, Wi-Max, IEEE 802.11 technology, radiofrequency (RF), Infrared Data Association (IrDA) compatible protocols,Local Area Networks (LAN), Wide Area Networks (WAN), Shared WirelessAccess Protocol (SWAP), any combinations thereof, and other types ofwireless networking protocols.

It should be understood that the foregoing figures and descriptionsillustrate non-limiting examples, and any suitable mechanism may be usedfor securing a mobile device to a docking station and for establishing acommunication link. Additionally, any mechanism for holding a mobiledevice may be ruggedized and/or weatherproof.

With reference again to FIG. 4, a mobile device used in connection withdocking station 1200 or another docking station may be appropriatelyprogrammed to log and generate electronic records of various markinginformation, which records may be formatted in various manners,processed and/or analyzed on the mobile device, and/or transmitted toanother device (e.g., a remote computer/server) for storage, processingand/or analysis. In one example, one or more pieces of geo-location data(e.g., from a GPS receiver, which may be integrated with the mobiledevice) may be collected and logged on the mobile device per actuationof a marking device (e.g., a trigger-pull to dispense marking material)in response to receipt by the mobile device of marking information.Furthermore, a computer-generated image or other visual representationof the marking operation may be electronically rendered in a displayfield of the mobile device based on logged marking information,essentially in real time as the marking operation is performed, and/orrecreated thereafter based on one or more stored electronic records.Various algorithms according to the concepts discussed herein may beavailable as “applications” that may be downloaded to the mobile deviceand selectable/operable from the user interface of the mobile device,such that the mobile device may also be used for other (moreconventional) functions (e.g., telephone calls, email, webaccess/browsing, etc.) in addition to specific functionality pursuant toexecution of docking station applications.

FIGS. 22A-26 and the corresponding portions of the specificationdescribe embodiments wherein a mobile computing device iscommunicatively coupled to a docking station. The docking station may beconfigured for mechanical and/or electronic docking of locatingequipment, such as a marking device or a combination locate and markingdevice. In further embodiments, the mobile computing device itselfserves as a docking station and performs one or more functionsassociated with operation of the marking device. In these embodiments,the mobile computing device is communicatively coupled to the markingdevice.

Referring to FIG. 27, a system including marking device 1250 and amobile computing device 1800 is shown. Mobile computing device 1800 iscommunicatively coupled to marking device 1250 by a cable 1810. In otherembodiments, mobile device 1800 may utilize wireless communication withmarking device 1250. In further embodiments, the system includes amarking device or a combination locate and marking device havingelectronic capabilities.

Mobile device 1800 may be programmed to perform one or more functions ofa docking station. For example, the mobile computing device 1800 maytransfer data, including but not limited to marking information, to andfrom the marking device, may log data received from the marking devicein a memory of the mobile computing device 1800, may process and/oranalyze the data received from the marking device, may communicate witha remote computing device, including transfer of data to and from theremote computing device, may perform data synchronization between themobile computing device 1800 and the marking device 1250, may serve as aterminal for user control of the marking device 1250, may displaymarking device information, such as for example status and jobinformation, may record a date and time of marking device operations,may record geographical coordinates, may execute a diagnostics routinefor testing of the marking device, may execute a calibration routine forcalibration of the marking device, may determine a charge state of thebattery in the marking device, may determine and verify an identity ofthe marking device, and/or may perform any other function associatedwith the marking device. These embodiments enable the mobile computingdevice to function as a docking station, without the mechanical dockingfunction described above. The mobile computing device 1800 may beprogrammed to perform one or more of the functions described above andto thereby function as a docking station. It will be understood that anyof the mobile devices described herein, including but not limited tomobile devices 1630, 1632, 1634, 1652, 1672, 1760 and 1800, may beprogrammed to perform one or more of the functions described above.Examples of mobile devices, such as cellular phones/PDAs, that aresuitable for purposes of embodiments using such mobile devices inconnection with docking stations include, but are not limited to,various models of the Apple iPhone (e.g., iPhone 3G S), various modelsof Blackberry® PDAs, various models of Windows® mobile phones bydifferent manufacturers, and various Android-based devices (“Android” isa mobile operating system running on the Linux kernel; it was initiallydeveloped by Google and later the Open Handset Alliance and allowsdevelopers to write managed code in the Java language, controlling thedevice via Google-developed Java libraries) available from a variety ofconventional mobile device suppliers (e.g., Motorola, Samsung,Sony-Ericsson). The connector for most Android-based devices typicallyis a standard micro USB connector. Connectors for other cellularphone/PDAs noted above may have various proprietary formats/pin layouts;an exemplary pin layout for an Apple iPhone is given in the followingtable (back side of dock connector; 2 4 6 8 10 12 14 16 18 20 22 24 2628 30; 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29; Pins 1,2 connected onmotherboard; Pins 15,16 connected on motherboard; Pins 19,20 connectedon motherboard; Pins 29,30 connected on motherboard):

Pin Signal Description 1 GND Ground (−), internaly connected with Pin 2on iPod motherboard 2 GND Audio & Video ground (−), internaly connectedwith Pin 2 on iPod motherboard 3 Right Line Out - R (+) (Audio output,right channel) 4 Left Line Out - L(+) (Audio output, left channel) 5Right In Line In - R (+) 6 Left In Line In - L (+) 8 Video Out Compositevideo output (only when slideshow active on iPod Photo) 9 S-Video ForiPod Color, Photo only Chrominance output 10 S-Video For iPod Color,Photo only Luminance output 11 GND Serial GND 12 Tx ipod sending line,Serial TxD 13 Rx ipod receiving line, Serial RxD 14 RSVD Reserved 15 GNDGround (−), internaly connected with pin 16 on iPod motherboard 16 GNDUSB GND (−), internaly connected with pin 15 on iPod motherboard 17 RSVDReserved 3.3 V Power (+) 18 3.3 V Stepped up to provide +5 VDC to USB oniPod Camera Connector. If iPod is put to sleep while Camera Connector ispresent, +5 VDC at this pin slowly drains back to 0 VDC. 19, 20 +12 VFirewire Power 12 VDC (+) 21 Accessory Different resistances indicateaccessory type: Indicator/Serial 1 kOhm - iPod docking station, beepswhen connected enable 10 kOhm - Takes some iPods into photo import mode68 kOhm - makes iPhone 3g send audio through line-out without anymessages 500 kOhm - related to serial communication/used to enableserial communications Used in Dension Ice Link Plus car interface 1MOhm - Belkin auto adaptor, iPod shuts down automatically when powerdisconnected Connecting pin 21 to ground with a 1 MOhm resistor doesstop the ipod when power (i.e. Firewire- 12 V) is cut. Looks to be thatwhen this pin is grounded it closes a switch so that on loss of powerthe Ipod shuts off. Dock has the same Resister. 22 TPA (−) FireWire DataTPA (−) 23 5 VDC (+) USB Power 5 VDC (+) 24 TPA (+) FireWire Data TPA(+) 25 Data (−) USB Data (−) 26 TPB (−) FireWire Data TPB (−) 27 Data(+) USB Data (+) Pins 25 and 27 may be used in different manner. Toforce the iPod 5G to charge in any case, when “USB Power 5 VDC” (pin 23)is fed, 25 must be connected to 5 V through a 10 kOhm resistor, and 27must be connected to the Ground (for example: pin 1) with a 10 kOhmresistor. iPod 5G can also be forced to charge by attaching the data +and the data − pins to the 5 v via a 10k Ohm resistor (BOTH PINS) andconnecting pin 16 to the 5 v (ground). (Confirmed working with iPod 5G20 GB) To charge an iPhone 3G/iPod Touch 2nd gen, usb data− (25) shouldbe at 2.8 v, usb data+(27) should be at 2.0 v. This can be done with afew simple resistors: 33k to +5 v (23) and 22k to gnd(16) to obtain 2 vand 33k to +5 v and 47k to gnd to obtain 2.8 v. This is a “notification”to the iphone that it is connected to the external charger and may drainamps from the usb. 28 TPB (+) FireWire Data TPB (+) 29, 30 GND FireWireGround (−)

While various inventive embodiments have been described and illustratedherein, those of ordinary skill in the art will readily envision avariety of other means and/or structures for performing the functionand/or obtaining the results and/or one or more of the advantagesdescribed herein, and each of such variations and/or modifications isdeemed to be within the scope of the inventive embodiments describedherein. More generally, those skilled in the art will readily appreciatethat all parameters, dimensions, materials, and configurations describedherein are meant to be exemplary and that the actual parameters,dimensions, materials, and/or configurations will depend upon thespecific application or applications for which the inventive teachingsis/are used. Those skilled in the art will recognize, or be able toascertain using no more than routine experimentation, many equivalentsto the specific inventive embodiments described herein. It is,therefore, to be understood that the foregoing embodiments are presentedby way of example only and that, within the scope of the appended claimsand equivalents thereto, inventive embodiments may be practicedotherwise than as specifically described and claimed. Inventiveembodiments of the present disclosure are directed to each individualfeature, system, article, material, kit, and/or method described herein.In addition, any combination of two or more such features, systems,articles, materials, kits, and/or methods, if such features, systems,articles, materials, kits, and/or methods are not mutually inconsistent,is included within the inventive scope of the present disclosure.

The above-described embodiments can be implemented in any of numerousways. For example, the embodiments may be implemented using hardware,software or a combination thereof. When implemented in software, thesoftware code can be executed on any suitable processor or collection ofprocessors, whether provided in a single computer or distributed amongmultiple computers.

Further, it should be appreciated that a computer may be embodied in anyof a number of forms, such as a rack-mounted computer, a desktopcomputer, a laptop computer, or a tablet computer. Additionally, acomputer may be embedded in a device not generally regarded as acomputer but with suitable processing capabilities, including a PersonalDigital Assistant (PDA), a smart phone or any other suitable portable orfixed electronic device.

Also, a computer may have one or more input and output devices. Thesedevices can be used, among other things, to present a user interface.Examples of output devices that can be used to provide a user interfaceinclude printers or display screens for visual presentation of outputand speakers or other sound generating devices for audible presentationof output. Examples of input devices that can be used for a userinterface include keyboards, and pointing devices, such as mice, touchpads, and digitizing tablets. As another example, a computer may receiveinput information through speech recognition or in other audible format.

Such computers may be interconnected by one or more networks in anysuitable form, including a local area network or a wide area network,such as an enterprise network, and intelligent network (IN) or theInternet. Such networks may be based on any suitable technology and mayoperate according to any suitable protocol and may include wirelessnetworks, wired networks or fiber optic networks.

A computer/computing device employed to implement various functionalitydescribed herein according to various embodiments may comprise a memory,one or more processing units (also referred to herein simply as“processors”), one or more communication interfaces, one or more displayunits, and one or more user input devices. The memory may comprise anycomputer-readable media, and may store computer instructions (alsoreferred to herein as “processor-executable instructions”) forimplementing the various functionalities described herein. Theprocessing unit(s) may be used to execute the instructions. Thecommunication interface(s) may be coupled to a wired or wirelessnetwork, bus, or other communication means and may therefore allow thecomputer to transmit communications to and/or receive communicationsfrom other devices. The display unit(s) may be provided, for example, toallow a user to view various information in connection with execution ofthe instructions. The user input device(s) may be provided, for example,to allow the user to make manual adjustments, make selections, enterdata or various other information, and/or interact in any of a varietyof manners with the processor during execution of the instructions.

The various methods or processes outlined herein may be coded assoftware that is executable on one or more processors that employ anyone of a variety of operating systems or platforms. Additionally, suchsoftware may be written using any of a number of suitable programminglanguages and/or programming or scripting tools, and also may becompiled as executable machine language code or intermediate code thatis executed on a framework or virtual machine.

In this respect, various inventive concepts may be embodied as acomputer readable storage medium (or multiple computer readable storagemedia) (e.g., a computer memory, one or more floppy discs, compactdiscs, optical discs, magnetic tapes, flash memories, circuitconfigurations in Field Programmable Gate Arrays or other semiconductordevices, or other non-transitory medium or tangible computer storagemedium) encoded with one or more programs that, when executed on one ormore computers or other processors, perform methods that implement thevarious embodiments of the invention discussed above. The computerreadable medium or media can be transportable, such that the program orprograms stored thereon can be loaded onto one or more differentcomputers or other processors to implement various aspects of thepresent invention as discussed above.

The terms “program” or “software” are used herein in a generic sense torefer to any type of computer code or set of computer-executableinstructions that can be employed to program a computer or otherprocessor to implement various aspects of embodiments as discussedabove. Additionally, it should be appreciated that according to oneaspect, one or more computer programs that when executed perform methodsof the present invention need not reside on a single computer orprocessor, but may be distributed in a modular fashion amongst a numberof different computers or processors to implement various aspects of thepresent invention.

Computer-executable instructions may be in many forms, such as programmodules, executed by one or more computers or other devices. Generally,program modules include routines, programs, objects, components, datastructures, etc. that perform particular tasks or implement particularabstract data types. Typically the functionality of the program modulesmay be combined or distributed as desired in various embodiments.

Also, data structures may be stored in computer-readable media in anysuitable form. For simplicity of illustration, data structures may beshown to have fields that are related through location in the datastructure. Such relationships may likewise be achieved by assigningstorage for the fields with locations in a computer-readable medium thatconvey relationship between the fields. However, any suitable mechanismmay be used to establish a relationship between information in fields ofa data structure, including through the use of pointers, tags or othermechanisms that establish relationship between data elements.

Also, various inventive concepts may be embodied as one or more methods,of which an example has been provided. The acts performed as part of themethod may be ordered in any suitable way. Accordingly, embodiments maybe constructed in which acts are performed in an order different thanillustrated, which may include performing some acts simultaneously, eventhough shown as sequential acts in illustrative embodiments.

All definitions, as defined and used herein, should be understood tocontrol over dictionary definitions, definitions in documentsincorporated by reference, and/or ordinary meanings of the definedterms.

The indefinite articles “a” and “an,” as used herein in thespecification and in the claims, unless clearly indicated to thecontrary, should be understood to mean “at least one.”

The phrase “and/or,” as used herein in the specification and in theclaims, should be understood to mean “either or both” of the elements soconjoined, i.e., elements that are conjunctively present in some casesand disjunctively present in other cases. Multiple elements listed with“and/or” should be construed in the same fashion, i.e., “one or more” ofthe elements so conjoined. Other elements may optionally be presentother than the elements specifically identified by the “and/or” clause,whether related or unrelated to those elements specifically identified.Thus, as a non-limiting example, a reference to “A and/or B”, when usedin conjunction with open-ended language such as “comprising” can refer,in one embodiment, to A only (optionally including elements other thanB); in another embodiment, to B only (optionally including elementsother than A); in yet another embodiment, to both A and B (optionallyincluding other elements); etc.

As used herein in the specification and in the claims, “or” should beunderstood to have the same meaning as “and/or” as defined above. Forexample, when separating items in a list, “or” or “and/or” shall beinterpreted as being inclusive, i.e., the inclusion of at least one, butalso including more than one, of a number or list of elements, and,optionally, additional unlisted items. Only terms clearly indicated tothe contrary, such as “only one of” or “exactly one of,” or, when usedin the claims, “consisting of,” will refer to the inclusion of exactlyone element of a number or list of elements. In general, the term “or”as used herein shall only be interpreted as indicating exclusivealternatives (i.e. “one or the other but not both”) when preceded byterms of exclusivity, such as “either,” “one of,” “only one of,” or“exactly one of” “Consisting essentially of,” when used in the claims,shall have its ordinary meaning as used in the field of patent law.

As used herein in the specification and in the claims, the phrase “atleast one,” in reference to a list of one or more elements, should beunderstood to mean at least one element selected from any one or more ofthe elements in the list of elements, but not necessarily including atleast one of each and every element specifically listed within the listof elements and not excluding any combinations of elements in the listof elements. This definition also allows that elements may optionally bepresent other than the elements specifically identified within the listof elements to which the phrase “at least one” refers, whether relatedor unrelated to those elements specifically identified. Thus, as anon-limiting example, “at least one of A and B” (or, equivalently, “atleast one of A or B,” or, equivalently “at least one of A and/or B”) canrefer, in one embodiment, to at least one, optionally including morethan one, A, with no B present (and optionally including elements otherthan B); in another embodiment, to at least one, optionally includingmore than one, B, with no A present (and optionally including elementsother than A); in yet another embodiment, to at least one, optionallyincluding more than one, A, and at least one, optionally including morethan one, B (and optionally including other elements); etc.

In the claims, as well as in the specification above, all transitionalphrases such as “comprising,” “including,” “carrying,” “having,”“containing,” “involving,” “holding,” “composed of,” and the like are tobe understood to be open-ended, i.e., to mean including but not limitedto. Only the transitional phrases “consisting of” and “consistingessentially of” shall be closed or semi-closed transitional phrases,respectively, as set forth in the United States Patent Office Manual ofPatent Examining Procedures, Section 2111.03.

What is claimed is:
 1. (canceled)
 2. A locate device docking station forholding, storing, and/or locking a locate device as used in a locateoperation to identify a presence or an absence of at least oneunderground facility in a dig area, wherein at least a portion of thedig area is to be excavated or disturbed during excavation activities,the locate device docking station comprising: a housing; a mobile deviceinterface to facilitate mechanical and electrical coupling and removalof a portable computing device; and a docking interface, operablycoupled to the housing, to mechanically receive the locate device andsubstantially hold the locate device when docked in the locate devicedocking station, wherein the docking interface comprises: acommunication interface to transmit data between the locate devicedocking station and the locate device; and a power interface to providepower from the locate device docking station to the locate device. 3.The locate device docking station of claim 2, further comprising: aprocessor; a user input device; and a memory, operably coupled to thecommunication interface, the processor, and the user input device, tostore processor-executable instructions and/or data received via thecommunication interface and/or the user input device.
 4. The locatedevice docking station of claim 3, wherein upon execution by theprocessor of the processor-executable instructions, the processorcontrols the communication interface to receive operating informationfrom the locate device when the locate device is docked in the dockingstation.
 5. The locate device docking station of claim 4, wherein theoperating information of the locate device comprises at least one of: abattery status of the locate device; a location of the locate device;and a user ID of a user from a list of approved users.
 6. The locatedevice docking station of claim 3, further comprising: a lockingmechanism to mechanically or electromagnetically secure the locatedevice to the locate device docking station when the locate device isdocked in the docking station.
 7. The locate device docking station ofclaim 6, wherein upon execution by the processor of theprocessor-executable instructions, the processor: controls the userinput device or the communication interface to receive firstidentification information of a user; and controls the locking mechanismto release the locate device if the first identification informationmatches second identification information, stored in the memory, of atleast one approved user.
 8. The locate device docking station of claim6, wherein upon execution by the processor of the processor-executableinstructions, the processor controls the locking mechanism to lock thelocate device, when the locate device is docked in the docking station,based at least in part on time information.
 9. The locate device dockingstation of claim 6, wherein upon execution by the processor of theprocessor-executable instructions, the processor controls the lockingmechanism to lock the locate device, when the locate device is docked inthe docking station, based at least in part on location information ofthe locate device.
 10. The locate device docking station of claim 2,wherein the communication interface comprises a wireless interface forwireless communication between the locate device and the locate devicedocking station.
 11. The locate device docking station of claim 2,further comprising: an identification reader, to read in identificationinformation of the locate device.
 12. The locate device docking stationof claim 11, wherein the identification reader comprises at least oneof: a radio frequency identification (RFID) reader; and a barcodereader.
 13. The locate device docking station of claim 2, furthercomprising: a mounting interface, operably coupled to the housing, tomount the locate device docking station to at least a portion of avehicle.
 14. The locate device docking station of claim 13, furthercomprising: a second power interface, operably coupled to the housing,to electrically couple the locate device docking station to anelectrical power system of the vehicle so as to receive power from thevehicle and to provide power to the power interface for the locatedevice.
 15. The locate device docking station of claim 2, furthercomprising the portable computing device communicatively coupled to thehousing via the mobile device interface, wherein the portable computingdevice comprises: a second processor; a second memory to storeprocessor-executable instructions; a display device to display at leasta portion of a graphic user interface (GUI); and a second communicationinterface, wherein the portable computing device is configured as a userterminal to control an operation of the locate device at least in partvia the GUI.
 16. An apparatus for holding, storing, and/or controlling alocate device as used in a locate operation to identify a presence or anabsence of at least one underground facility in a dig area, wherein atleast a portion of the dig area is to be excavated or disturbed duringexcavation activities, the apparatus comprising: a locate device dockingstation to dock the locate device, the locate device docking stationcomprising a mobile device interface to facilitate mechanical andelectrical coupling and removal of a portable computing device; and theportable computing device communicatively coupled to the locate devicedocking station via the mobile device interface, wherein the portablecomputing device comprises: a processor; a memory to storeprocessor-executable instructions; a display device to display at leasta portion of a graphic user interface (GUI); and a communicationinterface, wherein the portable computing device is configured as a userterminal to control an operation of the locate device.
 17. The apparatusof claim 16, wherein upon execution by the processor of theprocessor-executable instructions, the processor: controls thecommunication interface to receive a current date and time from a timingsystem attached to the locate device; and controls the memory to storethe current date and time.
 18. The apparatus of claim 17, wherein uponexecution by the processor of the processor-executable instructions, theprocessor: controls the communication interface to receive a geographiclocation information from a location tracking system attached to thelocate device; and controls the memory to store the geographic locationinformation.
 19. The apparatus of claim 18, wherein upon execution bythe processor of the processor-executable instructions, the processorcontrols the display device to display a real-time manifest of thegeographic location information received from the communicationinterface.
 20. The apparatus of claim 16, wherein upon execution by theprocessor of the processor-executable instructions, the processor:controls the communication interface to receive a locate signalinformation from a locate receiver attached to the locate device; andcontrols the memory to store the locate signal information.
 21. Theapparatus of claim 20, wherein upon execution by the processor of theprocessor-executable instructions, the processor controls the displaydevice to display a real-time manifest of the locate signal informationreceived from the communication interface.
 22. The apparatus of claim16, wherein upon execution by the processor of the processor-executableinstructions, the processor controls the GUI to receive a user inputfrom an operator so as to control an operation of the locate deviceduring the locate operation.
 23. A locate device docking station forholding, storing, and/or locking a locate device as used in a locateoperation to identify a presence or an absence of at least oneunderground facility in a dig area, wherein at least a portion of thedig area is to be excavated or disturbed during excavation activities,the locate device docking station comprising: a housing; a portablecomputing device removably coupled to the housing, the portablecomputing device comprising: a processor; a memory to storeprocessor-executable instructions; a communication interface; and adisplay device to display at least a portion of a graphic user interface(GUI); and a docking interface, operably coupled to the housing andcommunicatively coupled to the portable computing device, tomechanically receive the locate device and substantially hold the locatedevice when docked in the locate device docking station, wherein thelocate device docking station is configured to control an operation ofthe locate device via at least one of the GUI and the communicationinterface.
 24. The locate device docking station of claim 23, whereinupon execution by the processor of the processor-executableinstructions, the processor controls the GUI to receive a user inputfrom an operator so as to control an operation status of the locatedevice during the locate operation.
 25. The locate device dockingstation of claim 23, wherein upon execution by the processor of theprocessor-executable instructions, the processor controls the at leastone communication interface to control an operation status of the locatedevice during the locate operation according to operating parametersstored in the memory.
 26. The locate device docking station of claim 23,wherein upon execution by the processor of the processor-executableinstructions, the processor controls the GUI to receive first useridentification information from an operator; controls the at least onecommunication interface to disable the locate device if the first useridentification information does not match second user identificationinformation, stored in the memory, of at least one approved user.